This looks very like the log recovery code and the raid code are not
playing well with each other - which is a problem. If you actually
run repair on the filesystem, it will zero the log and you should
be able to mount it.
before doing that can you run:
xfs_logprint -t -i -b -e /dev/md0
and send me the output, logprint may well crash doing this.
Steve
> Hi,
>
> Kernel: 2.4.7-pre8 (cvs from 19-07-2001 evening, CET)
>
> After an AC failure, I can't mount my raid5, I get
> (/users is on fstab: /dev/md0)
>
>
> juno-tty1:~# mount /users
> Start mounting filesystem: md(9,0)
> Starting XFS recovery on filesystem: md(9,0) (dev: 9/0)
> XFS: xlog_recover_process_data: bad clientid
> XFS: log mount/recovery failed
> XFS: log mount failed
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
> or too many mounted file systems
>
>
> And on the /var/log/messages:
>
>
> Jul 20 11:38:17 juno kernel: Start mounting filesystem: md(9,0)
> Jul 20 11:38:17 juno kernel: Starting XFS recovery on filesystem: md(9,0) (de
> v: 9/0)
> Jul 20 11:38:17 juno kernel: XFS: xlog_recover_process_data: bad clientid
> Jul 20 11:38:17 juno kernel: XFS: log mount/recovery failed
> Jul 20 11:38:17 juno kernel: XFS: log mount failed
>
>
> I run xfs_repair -n /dev/md0, but I don't see anything wrong... (I think...)
>
> What can I do? I've lost all my data?
>
> Thanx in advance.
>
> /Fermin
|