linux@xxxxxxxxxxx wrote:
> I've been having hard-to-reproduce sata_sil24 driver problems, and
> the most recent lockup appears to have taken out my root file system.
> (Hooray for emergency boot partitions!)
>
> # mount -r /dev/md4 /mnt
> mount: /dev/md4: can't read superblock
>
> With the following appended to the kernel log:
>
> XFS mounting filesystem md4
> Starting XFS recovery on filesystem: md4 (dev: md4)
> XFS: xlog_recover_process_data: bad clientid
> XFS: log mount/recovery failed: error 5
> XFS: log mount failed
>
> I haven't put this server into production yet (due to aforementioned
> libata issues), so I'm experiementing with XFS, but this failure isn't
> confidence-inspiring.
Is the problematic filesystem on the aforementioned flakey driver?
Any kernel messages prior to the fs problems? (related to underlying IO
problems?)
-Eric
|