From: Ric Wheeler <rwheeler@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Theodore Tso <tytso@mit.edu>,
Parag Warudkar <parag.lkml@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14354] Re: ext4 increased intolerance to unclean shutdown?
Date: Mon, 26 Oct 2009 09:49:14 -0400 [thread overview]
Message-ID: <4AE5A8DA.3040209@redhat.com> (raw)
In-Reply-To: <20091025062202.GB1391@ucw.cz>
On 10/25/2009 02:22 AM, Pavel Machek wrote:
> Hi!
>
>>>> So I have been experimenting with various root file systems on my
>>>> laptop running latest git. This laptop some times has problems waking
>>>> up from sleep and that results in it needing a hard reset and
>>>> subsequently unclean file system.
>>>>
>>> A number of people have reported this, and there is some discussion
>>> and some suggestions that I've made here:
>>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=14354
>>>
>>> It's been very frustrating because I have not been able to replicate
>>> it myself; I've been very much looking for someone who is (a) willing
>>> to work with me on this, and perhaps willing to risk running fsck
>>> frequently, perhaps after every single unclean shutdown, and (b) who
>>> can reliably reproduce this problem. On my system, which is a T400
>>> running 9.04 with the latest git kernels, I've not been able to
>>> reproduce it, despite many efforts to try to reproduce it. (i.e.,
>>> suspend the machine and then pull the battery and power; pulling the
>>> battery and power, "echo c> /proc/sysrq-trigger", etc., while
>>> doing "make -j4" when the system is being uncleanly shutdown)
>>>
>>
>> I wonder if we might have better luck if we tested using an external
>> (e-sata or USB connected) S-ATA drive.
>>
>> Instead of pulling the drive's data connection, most of these have an
>> external power source that could be turned off so the drive firmware
>> won't have a chance to flush the volatile write cache. Note that some
>> drives automatically write back the cache if they have power and see a
>> bus disconnect, so hot unplugging just the e-sata or usb cable does not
>> do the trick.
>>
>> Given the number of cheap external drives, this should be easy to test
>> at home....
>
> Do they support barriers?
>
> (Anyway, you may want to use some kind of VM for testing. That should
> make the testing cycle shorter, easier to reprorduce *and* more repeatable.)
>
> Pavel
>
The drives themselves will support barriers - they are the same S-ATA/ATA drives
you get normally for your desktop, etc.
I think that e-SATA would have no trouble (but fewer boxes have that external
S-ATA port). Not sure how reliable the SCSI -> USB -> ATA conversion is for USB
drives though (a lot of moving pieces there!).
VM testing is a good idea, but I worry that the virtual IO stack support for
data integrity is still somewhat shaky. Christoph was working on fixing various
bits and pieces I think...
ric
next prev parent reply other threads:[~2009-10-26 13:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 4:28 ext4 increased intolerance to unclean shutdown? Parag Warudkar
2009-10-16 6:31 ` Maxim Levitsky
2009-10-16 9:15 ` [Bug 14354] " Theodore Tso
2009-10-16 13:06 ` Theodore Tso
2009-10-16 19:16 ` Ric Wheeler
2009-10-25 6:22 ` Pavel Machek
2009-10-26 13:49 ` Ric Wheeler [this message]
2009-10-16 22:24 ` Parag Warudkar
2009-10-16 22:24 ` Parag Warudkar
2009-10-26 15:42 ` Linus Torvalds
2009-10-27 10:15 ` Aneesh Kumar K.V
2009-10-29 20:10 ` Mingming
2009-10-29 21:25 ` Parag Warudkar
2009-10-29 21:25 ` Parag Warudkar
2009-10-29 21:38 ` Eric Sandeen
2009-10-30 8:16 ` Theodore Tso
2009-10-30 13:54 ` Eric Sandeen
2009-10-30 13:54 ` Eric Sandeen
2009-10-30 19:56 ` Andreas Dilger
2009-10-31 9:15 ` Theodore Tso
2009-10-31 15:24 ` Aneesh Kumar K.V
2009-10-31 15:24 ` Aneesh Kumar K.V
2009-10-29 21:42 ` Theodore Tso
2009-10-29 21:42 ` Theodore Tso
2009-10-29 21:52 ` Parag Warudkar
2009-10-29 21:52 ` Parag Warudkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE5A8DA.3040209@redhat.com \
--to=rwheeler@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.lkml@gmail.com \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.