See the attached screenshot - this one is from a mounted ddrescue image with
zeroes instead of bad blocks. 8 of them (4kB of data) were damaged. And yes,
ddrescue reported read errors, so did the kernel (dmesg) and extended SMART
test also failed on the problematic sectors.
Bye,
Samo Vodopivec
> -----Original Message-----
> From: Bruce Allen [mailto:ballen@...]
> Sent: Thursday, December 18, 2008 4:45 PM
> To: Samo Vodopivec
> Cc: Douglas Gilbert; Smartmontools Mailing List
> Subject: RE: [smartmontools-support] Bad block HOWTO for XFS
>
> Samo, well done! This is a very useful transcript for anyone else who
> wants to identify files with bad blocks.
>
> Were you able to check that this was the bad file, eg by
>
> cat /usr/src/linux-2.6.27/drivers/scsi/st.c > /dev/null
>
> and then seeing an IO error?
>
> Cheers,
> Bruce
>
>
> On Thu, 18 Dec 2008, Samo Vodopivec wrote:
>
> > Hello,
> >
> > yes, I was able to identify the bad file on my XFS, see the attached txt
> > file as a sample (there are two samples in that file, both showing the
> > search for the same sector, but the second one is a little shorter).
123123
> > is the LBA address inside the /dev/sda1 device (counted from beginning
of
> > partition). I was quite lucky and got the right address from dmesg
output -
> > it was showing both the absolute sector address on sda device and the
> > relative sector address inside the sda1 device (so no hand made
calculations
> > were necessary).
> >
> > And before you ask:
> > - the sample in the txt file is made in vmware
> > - the partition was not mounted (it does not work on live filesystem)
> > - the same thing works also with partition images (use -f flag) made
with
> > ddrescue
> >
> > Bye,
> >
> > Samo Vodopivec
> >
> >> -----Original Message-----
> >> From: Bruce Allen [mailto:ballen@...]
> >> Sent: Thursday, December 18, 2008 12:13 PM
> >> To: Gabriele Pohl; Douglas Gilbert; Samo Vodopivec
> >> Cc: Smartmontools Mailing List
> >> Subject: Re: [smartmontools-support] Bad block HOWTO for XFS
> >>
> >> Samo: thank you! By the way, there is a more current version of the
> >> how-to, but it does not handle the XFS case. It's the second link
below.
> >>
> >> Gabi: could you please add something to this file:
> >> http://smartmontools.sourceforge.net/BadBlockHowTo.txt
> >> which references the more current version:
> >> http://smartmontools.sourceforge.net/badblockhowto.html
> >> and check that the smartmontools web pages are referencing the SECOND
of
> >> these URLs, not the first.
> >>
> >> Doug: would you have time to incorporate the XFS information referenced
> >> below by Samo (http://www.nabble.com/Find-file-for-inode-td670154.html)
> >> into the current badblockshowto document? It's not clear if this will
> >> really work in the real world. The story recounted in the URL ends
with
> >> the user NOT able to identify the file stored at the bad block
location.
> >> But at least in principle this might work.
> >>
> >> Samo: were you able to identify the bad file on your XFS filesystem?
> >>
> >> Cheers,
> >> Bruce
> >>
> >>
> >>
> >> On Wed, 17 Dec 2008, Samo Vodopivec wrote:
> >>
> >>> Hello,
> >>>
> >>>> From the Bad Block HOWTO: "The authors would like to add text showing
> > how
> >> to
> >>> do this for other file systems, in particular XFS, and JFS: please
email
> > if
> >>> you can provide this information."
> >>>
> >>> The XFS sample can be found here:
> >>> http://www.nabble.com/Find-file-for-inode-td670154.html
> >>>
> >>> Bye,
> >>>
> >>> Samo Vodopivec
> >>> ------------------------------
> >>>
> >>> You may say I'm a dreamer, but I'm not the only one.
> >>>
> >>> by John Lennon
> >>>
> >>>
> >>>
> >>>
> >>>
> >
----------------------------------------------------------------------------
> > --
> >>> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
> > Nevada.
> >>> The future of the web can't happen without you. Join us at MIX09 to
> > help
> >>> pave the way to the Next Web now. Learn more and register at
> >>>
> >
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> >>> _______________________________________________
> >>> Smartmontools-support mailing list
> >>> Smartmontools-support@...
> >>> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
> >>>
> >
|