Re: regarding bug #5914 - fs corruption on SATA

[Jens Axboe <axboe@suse.de>]

On Tue, Jan 31 2006, Nicolas Mailhot wrote:
> 
> Le Mar 31 janvier 2006 08:26, Jens Axboe a écrit :
> > On Tue, Jan 31 2006, Nicolas Mailhot wrote:
> >> Le lundi 30 janvier 2006 à 16:08 +0100, Jens Axboe a écrit :
> >> > On Sat, Jan 28 2006, Nicolas Mailhot wrote:
> >> > > I can confirm today's patch is not OK. The same baseline with
> >> > > yesterday's patch boot fine.
> >> >
> >> > Is this any better?
> >>
> >> This one seems to work fine.
> >
> > And you don't get "w/ FUA" messages from the problematic drives - and
> > your data appears safe? Just checking, we cannot take these corruption
> > things lightly.
> 
> I didn't spend a lot of time on this, the build finished rather late
> in the evening/night. What I can say is the dramatic breakage I had
> before is gone and I don't think there was any error in dmesg (will
> post it this evening if you want). With dm+raid when FUA broke things
> it was difficult to miss (screenfulls of ATA/raid errors, fs
> corruption on reboot, etc)
> 
> Now if you ask me if I did some heavy I/O to stress the system no I
> didn't yet. If problems still lurk they are a lot less extensive than
> they were before. I did trigger a full FS autorelabel so at least the
> read part was tested a bit.

Sounds like it works, if you saw the errors so quickly. Just trying to
be absolutely sure, if you could check for the "w/ FUA" prints not being
there now it would confirm that the blacklist does its job.

-- 
Jens Axboe