Harry Mangalam wrote:
> mount -t xfs -o loop,offset=11403264,ro,norecovery /dev/md0 /lost
>
> gives me a mount(!!):
>
> df -> /lost/public, but it's not a standard entry:
> ?--------- ? ? ? ? ? /lost/public
>
> and dmesg coughs up many lines of XFS errors:
not sure at this point. i'd put it back in the nas box w/ the recreated
raid mount -o ro,norecovery again for safety if you like, and hope for
the best.
Otherwise maybe run repair; on a dd image if you prefer, again for
safety....
-Eric
> loop: AES key scrubbing enabled
> loop: loaded (max 8 devices)
> Filesystem "loop0": Disabling barriers, not supported by the
> underlying device
> Mounting filesystem "loop0" in no-recovery mode. Filesystem will be
> inconsistent.
> XFS resetting qflags for filesystem loop0
> xfs_force_shutdown(loop0,0x1) called from line 424 of file
> fs/xfs/xfs_rw.c. Return address = 0xfb2fc728
> Filesystem "loop0": I/O Error Detected. Shutting down filesystem:
> loop0
> Please umount the filesystem, and rectify the problem(s)
> xfs_force_shutdown(loop0,0x1) called from line 424 of file
> fs/xfs/xfs_rw.c. Return address = 0xfb2fc728
> Filesystem "loop0": Disabling barriers, not supported by the
> underlying device
> Mounting filesystem "loop0" in no-recovery mode. Filesystem will be
> inconsistent.
> XFS resetting qflags for filesystem loop0
>
>
>
>
> On Monday 23 February 2009, Eric Sandeen wrote:
>> try mount -o loop,offset=11403264 /dev/whatever /mnt/whatever
>>
>> I'd probably also add ro,norecovery to the options as well so you
>> don't actually write anything to it at this point.
>>
>> -Eric
>
>
>
|