All of lore.kernel.org
 help / color / mirror / Atom feed
From: Default User <default_user@email.it>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair 3.1.1 doesnt repair broken filesystem
Date: Tue, 18 May 2010 13:01:47 +0200	[thread overview]
Message-ID: <4BF2739B.6000509@email.it> (raw)
In-Reply-To: <201005180953.51892@zmi.at>

On 05/18/2010 09:53 AM, Michael Monnerie wrote:
> I do a repair on a broken filesystem, which reports no problems. Then I
> mount and "ls -l", and you can easily see all those broken entries,
> which should be directories. They are not repaired. What could I do?
>    

I think you have created the filesystem with -o inode64 and now you are 
remounting it without -o inode64.
After you created one file or directory with the inode64 option you NEED 
to always specify inode64 option at subsequent mounts or you won't be 
able to access such files/directories.
(Not sure if forgetting to use the option can even cause data corruption 
upon write. Might inode32 writes overwrite the inaccessible inode64 
files/dirs? XFS developers might know this.)

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-05-18 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  7:53 xfs_repair 3.1.1 doesnt repair broken filesystem Michael Monnerie
2010-05-18 10:16 ` Emmanuel Florac
2010-05-18 11:01 ` Default User [this message]
2010-05-18 11:42   ` xfs_repair 3.1.1 doesnt repair broken filesystem [solved] Michael Monnerie

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=4BF2739B.6000509@email.it \
    --to=default_user@email.it \
    --cc=michael.monnerie@is.it-management.at \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.