Re: mount: Function not implemented

[Eric Sandeen <sandeen@sandeen.net>]

David Chinner wrote:
> On Thu, Dec 13, 2007 at 04:46:18PM +0100, KE Liew wrote:

>> The hexdump:
>> ===================
>> # dd if=/dev/hdb bs=512 count=1 | hexdump -C
>> 1+0 records in
>> 1+0 records out
>> 00000000  58 46 53 42 00 01 00 00  00 00 00 00 00 3a 38 b0
>> |XFSB.........:8.|
> 
> This kind of indicates that you did a 'mkfs.xfs /dev/hdb' not
> the partition you created. If that is the case, then rebooting
> may have written who-knows-what to disk.

although if it was a) new and b) he made a whole-disk partition, it was
probably not a busy disk and I wouldn't expect a reboot was necessary.

>> The xfs_db:
>> ===================
>> # xfs_db -r -c "sb 0" -c p /dev/hdb
>> cache_node_purge: refcount was 1, not zero (node=0x80ca410)
>> xfs_db: cannot read root inode (22)
> 
> EINVAL.

Hm, that should probably use perror or something, silly me read that as
the inode *number* and then thought "hmm I bet something stuck EINVAL
into the inode number, oops!"  :)

>> cache_node_purge: refcount was 1, not zero (node=0x80da608)
>> xfs_db: cannot read realtime bitmap inode (22)
>> Segmentation fault
>> ===================
> 
> That tends to indicate that the filesystem superblock is ok but
> the contents are not.
> 
> Without knowing exactly what you did and what errors came up, it's
> going to be hard reconstructing what went wrong. Perhaps a metadump
> of the filesysetm woul dbe useful in working out how it is broken....

Metadump failed with the same errors as xfs_db

-Eric