[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200910170601.n9H61kB3006548@demeter.kernel.org>
Date: Sat, 17 Oct 2009 06:01:46 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 #71 from Alexey Fisher <bug-track@...her-privat.net> 2009-10-17 06:01:45 ---
you don't have to edit init script, all you need is to boot with "break=mount".
On ubuntu/debian this will stop boot in initrd without mounted root. After
this you can mount it read only or what ever you need. But you can't fsck it,
initrd do not include such tools. Continue:
mount -o ro /dev/sda1_your_root /root
mount -o bind /dev /root/dev
chroot /root /bin/bash
now you'll have clean mount without any other corruptions caused by init script
bug.
Please can anyone place this "auto_da_alloc=0". On my system this work around
data lost issue. Can any one confirm this too?
--
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