[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200910112145.n9BLjYWV015325@demeter.kernel.org>
Date: Sun, 11 Oct 2009 21:45:34 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards
http://bugzilla.kernel.org/show_bug.cgi?id=14354
--- Comment #15 from Alexey Fisher <bug-track@...her-privat.net> 2009-10-11 21:45:34 ---
Yes, i had read-only problem too, but i can't reproduce it now. I had some
trouble to mount system and fsck it, some important files was corrupt. Suddenly
all i wanted is to make it work again.. so there is not dmesg after it.
On my major PC i used debsums to find broken files and reinstall this. On my
laptop i didn't had so mach luck, the packagebase was corrupted so i
reformatted and reinstall the system. I can try to go back to 2.6.32-rcX and
use it until next crush, but i need to know what to do, to extrakt all
information will need for this bug. Thirst good idea will be probably remote
syslog server.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists