From: Eric Sandeen <sandeen@sandeen.net>
To: David Chinner <dgc@sgi.com>
Cc: Thomas Walker <walker@stsci.edu>, xfs@oss.sgi.com
Subject: Re: Should xfs_repair take this long?
Date: Fri, 16 Mar 2007 14:30:41 -0500 [thread overview]
Message-ID: <45FAF061.8070800@sandeen.net> (raw)
In-Reply-To: <20070316192037.GZ5743@melbourne.sgi.com>
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*
next prev parent reply other threads:[~2007-03-16 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 0:20 Should xfs_repair take this long? Thomas Walker
2007-03-16 1:32 ` David Chinner
2007-03-16 11:15 ` Thomas Walker
2007-03-16 19:20 ` David Chinner
2007-03-16 19:30 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-16 20:09 Thomas Walker
2007-03-16 20:52 ` David Chinner
2007-03-15 11:27 Thomas Walker
2007-03-15 14:04 ` Emmanuel Florac
2007-03-15 14:06 ` Thomas Walker
[not found] ` <20070315160309.652a6e0c@harpe.intellique.com>
[not found] ` <45F96150.50001@stsci.edu>
2007-03-15 15:23 ` Emmanuel Florac
2007-03-15 15:27 ` Thomas Walker
2007-03-15 23:10 ` David Chinner
2007-03-16 15:15 ` Thomas Walker
2007-03-16 19:37 ` David Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45FAF061.8070800@sandeen.net \
--to=sandeen@sandeen.net \
--cc=dgc@sgi.com \
--cc=walker@stsci.edu \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox