xfs
[Top] [All Lists]

Re: Should xfs_repair take this long?

To: David Chinner <dgc@xxxxxxx>
Subject: Re: Should xfs_repair take this long?
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 16 Mar 2007 14:30:41 -0500
Cc: Thomas Walker <walker@xxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20070316192037.GZ5743@melbourne.sgi.com>
References: <20070315202027.CNS24438@comet.stsci.edu> <20070316013227.GO5743@melbourne.sgi.com> <45FA7C37.4070001@stsci.edu> <20070316192037.GZ5743@melbourne.sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
David Chinner wrote:
On Fri, Mar 16, 2007 at 07:15:03AM -0400, Thomas Walker wrote:
No problem. The error was with the iflag=direct, apparently RHEL4 doesn't like that option so I took it out. Here's the output from each of the xfs volumes;

[root@hla-ags ~]# dd if=/dev/mapper/vg0-hladata3 bs=512 count=1 | od -Ax -x
1+0 records in
1+0 records out
000000 0000 6419 0000 0c00 0000 7419 0000 0c00
000010 0000 8419 0000 0c00 0000 9419 0000 0c00

That's not a XFS superblock :(

lmdd pattern?

[root@hla-ags ~]# dd if=/dev/mapper/vg1-hladata2 bs=512 count=1 | od -Ax -x
1+0 records in
000000 7970 6f72 746f 203a 2030 0a2f 500a 414c
000010 4e49 4b0a 3120 410a 560a 3120 0a34 6964
000020 2072 2e31 2e30 3572 392f 3830 4b0a 3420
000030 690a 746f 0a61 2056 3531 660a 6c69 2065

Neither is that - it's a bunch of text that doesn't make much sense to me....

[esandeen@neon ~]$ echo "pyroot" | hexdump 0000000 7970 6f72 746f 000a

python?

*shrug*


<Prev in Thread] Current Thread [Next in Thread>