public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Madan Valluri <mvalluri@sgi.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Barry Naujok <bnaujok@melbourne.sgi.com>, xfs@oss.sgi.com
Subject: Re: Review: xfs_repair fixes for dir2 corruption
Date: Fri, 28 Jul 2006 07:45:12 -0700	[thread overview]
Message-ID: <44CA22F8.2040507@sgi.com> (raw)
In-Reply-To: <20060728181013.C2197701@wobbly.melbourne.sgi.com>

Nathan Scott wrote:
> On Fri, Jul 28, 2006 at 11:58:52AM +1000, Barry Naujok wrote:
>   
>> This patch addresses the following xfs_repair issues:
>>     
>
> The libxfs cache stuff looks good to me.  Maybe Madan can cast
> an eye over the repair changes for ya?
>
> cheers.
>
>   
>>  
1) Since dir_hash_add can be called for both V1 and V2 directories its 
second parameter type xfs_dir2_dataptr_t should be neutral.
2) In dir_hash_add when dup is set, do you still need to add to the 
nextbyhash by list?
3) The following statement in   longform_dir2_rebuild looks odd. 
Besides, FWIW, you can match "/."

                if (p->name[0] == '/' || (p->name[0] == '.' && 
(p->namelen == 1
                                || (p->namelen == 2 && p->name[1] == '.'))))
                        continue;

Consider:

               if (((p->name[0] == '/' || p->name[0] == '.') && 
p->namelen == 1) ||
                        (p->name[0] == '.' && p->name[1] == '.' && 
p->namelen == 2))
                        continue;

4) Related to items 2&3, shouldn't the code be skipping duplicate entries?
5) Can we do anything to minimize the do_error calls in 
longform_dir2_rebuild? Seems like on a full file system, while 
rebuilding say the root directory, matters can get wacky - The directory 
is being rebuilt and we have no further room. Sounds like that this how 
it has been....

Thanks.

/Madan

  reply	other threads:[~2006-07-28 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  3:50 review: increase bulkstat readahead window Nathan Scott
2006-07-25  9:40 ` Christoph Hellwig
2006-07-25 22:37   ` Nathan Scott
2006-07-26 10:25     ` Christoph Hellwig
2006-07-27 23:17       ` Nathan Scott
2006-07-28  1:58         ` Review: xfs_repair fixes for dir2 corruption Barry Naujok
2006-07-28  8:10           ` Nathan Scott
2006-07-28 14:45             ` Madan Valluri [this message]
2006-07-31  7:18               ` Barry Naujok
2006-07-30  5:19           ` christian
2006-08-01 21:50           ` Adam Sjøgren
2006-08-01 23:06             ` Christian Guggenberger

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=44CA22F8.2040507@sgi.com \
    --to=mvalluri@sgi.com \
    --cc=bnaujok@melbourne.sgi.com \
    --cc=nathans@sgi.com \
    --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