[mythtv-users] Is my JFS broken ?

[Ian Clark]

2008/8/25 r2d2 <r2d2z4j6y8 at gmail.com>

>
> [snip me]
>
> I choose creating a new fs as I think the JFS filesystem is definitely
> corrupted. Most of you are thinking of software troubleshooting, so I will
> prefer EXT3 for this new fs. It is less efficient for recordings (big files)
> but more robust, I think.
>

I can't really comment on this, although isn't JFS an IBM thing? I suspect
it's fairly robust (it's part of AIX after all, and that's a proper unix
*ducks*) I don't know about the code in linux though.

Mind you, I suspect that unless your i/o is aproaching the limits on your
system (which if you're recording tv it almost certantly isn't) you'll not
notice any issues. (I'm using ext3 for both my recording drives fwiw; if
you're interested I can probably dig out the IO stats.)

>
> So as to be sure it is not a hardware issue, I used badblocks as mentioned
> by Alex.
>
> badblocks -n -s /dev/sdb
> Checking for bad blocks (non-destructive read-write test)
> Testing with random pattern: done
>
> I also used smartctl -t long /dev/sdb which doesn't log any error. So I
> think the harddisk is healthy. I am going to apply this check on the other
> harddisk to be sure it is a software troubleshooting.
>

Sounds like it.

>
> Shouldn't smartctl be enough ?
>

Nope. There are many errors that SMART can't detect, or failures that happen
so quickly that the drive is dead before it does.

>
> Is there a best way to check harddisk ?
>
>
badblocks sounds like a good way. you could probably do something like:

dd if=/dev/hd0 of=/dev/null

and check for read errors too, but the reality is modern harddiscs tend to
either last for ages until they wear out or go very quickly. If you've got
RAID5 or 1 (it is 1 that's striped isn't it?) you should detect the error
before you loose the data.

Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080827/c055d091/attachment.htm