public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: [PATCH V2] xfs_repair: print superblock offsets and why they can't	be verified
Date: Thu, 23 Oct 2008 09:24:35 -0500	[thread overview]
Message-ID: <49008923.7030208@sandeen.net> (raw)
In-Reply-To: <490081C6.1030301@sandeen.net>

Eric Sandeen wrote:
> KELEMEN Peter wrote:
>> Eric has pointed out that verify_set_primary_sb() will either
>> return 1 or XR_INSUFF_SEC_SB.  Move the check lower into
>> verify_set_primary_sb() by checking the return value of
>> verify_sb().  Example output:
>>
>> found candidate secondary superblock...
>> verifying sb at 31249334272: bad magic number (1)
>> verifying sb at 62498668544: bad magic number (1)
>> verifying sb at 93748002816: bad magic number (1)
>> verifying sb at 124997337088: bad magic number (1)
>> unable to verify superblock, continuing...
>>
> 
> This looks better :)  You may want to add even more info...
> 
> while it's just searching block by block, if it finds a candidate, I'd
> print the sector offset for that candidate (your first output line).
> 
> And rather than "verifying sb at..." you might do something like
> "comparing to sb N at offset X":
> 
> +	} else {
> +		do_warn("comparing with sb %d at sector %Lu failed: %s (%d)\n",
> +			agno, off, err_string(reason), reason);

Sorry, that was a pre-coffee email :)  The units are bytes, not sectors,
aren't they... in any case, printing the (proper) units for the values
would be helpful.

-Eric

  reply	other threads:[~2008-10-23 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 18:36 [PATCH] xfs_repair: print superblock offsets and denial reasons KELEMEN Peter
2008-10-22 23:41 ` [PATCH V2] xfs_repair: print superblock offsets and why they can't be verified KELEMEN Peter
2008-10-23 13:53   ` Eric Sandeen
2008-10-23 14:24     ` Eric Sandeen [this message]
2008-11-21  1:03     ` Barry Naujok

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=49008923.7030208@sandeen.net \
    --to=sandeen@sandeen.net \
    --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