All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <xfs@tlinx.org>
To: Michael Weissenbacher <mw@dermichi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs file system in process of becoming corrupt; though	xfs_repair	thinks it's fine! ; -/ (was xfs_dump problem...)
Date: Tue, 29 Jun 2010 17:42:02 -0700	[thread overview]
Message-ID: <4C2A92DA.1020202@tlinx.org> (raw)
In-Reply-To: <4C2A87FF.7090804@dermichi.com>



Michael Weissenbacher wrote:
> Hi!
>>> 2359101 ?????????? ? ? ? ?                ? 30-Omoide to Yakusoku (TV saizu｜Reinaʼs Ver.).mp3
>>> 2354946 ?????????? ? ? ? ?                ? 31-Omoide to Yakusoku (TV saizu｜Tomoeʼs Ver.).mp3
>>> 2354949 ?????????? ? ? ? ?                ? 32-Omoide to Yakusoku (TV saizu｜Nanualʼs Ver.).mp3
>>> ls: cannot access bad2/30-Omoide to Yakusoku (TV saizu｜Reinaʼs Ver.).mp3: No such file or directory
>>> ls: cannot access bad2/31-Omoide to Yakusoku (TV saizu｜Tomoeʼs Ver.).mp3: No such file or directory
>>> ls: cannot access bad2/32-Omoide to Yakusoku (TV saizu｜Nanualʼs Ver.).mp3: No such file or directory
>> ...
>>
>> If there are no problems reported by repair, then I suspect that
>> it's a terminal level problem...
>>
> Looking at this i remember having similar problems when my filesystems
> was mounted with inode64 before and after i left out that parameter. So
> Linda, could you re-try mounting the fs with "inode64".
----
	I ran into that before as well -- already tried

Notice the listing you see is the output of "ls -in".
Those numbers are the inodes.  ...HEY, wait.
When do you need 64-bit inodes?  The dump size said it was:
xfsdump: estimated dump size: 2360915740992 bytes

It's getting right near to overflowing a 32-bit integer.

Do I need >32 bit inodes if the filesystem size is > 2T?

I'm guessing the file system just recently passed the 2G mark.
Note -- I DID try the inode64 mount option -- it made no difference.


But if you need 64-bit inodes for file systems > 2T file systems,
then shouldn't I have gotten some error rather than it eating files
for lunch?

The inode numbers themselves, are not even close to being over 32bits.  

Sigh...


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

  reply	other threads:[~2010-06-30  0:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-27  1:10 WARNING xfsdump [still] Cannot allocate memory for list of [root|non-root] attributes for nondir ino xxyz Linda A. Walsh
2010-06-28  2:27 ` Dave Chinner
2010-06-29 22:33   ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Linda Walsh
2010-06-29 23:25     ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-29 23:55       ` Michael Weissenbacher
2010-06-30  0:42         ` Linda A. Walsh [this message]
2010-06-30  1:16           ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Dave Chinner
2010-06-30  2:45             ` Linda A. Walsh
2010-07-01 23:58               ` Dave Chinner
2010-07-07  3:18                 ` Linda A. Walsh
2010-07-07  5:56                   ` Linda Walsh
2010-07-07  6:36                     ` Dave Chinner
2010-07-07  9:30                       ` Linda A. Walsh
2010-07-07 21:01                         ` Linda Walsh
2010-06-30  0:01       ` Linda A. Walsh
2010-06-30  1:06         ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-30  1:52           ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30 21:01             ` Stan Hoeppner
2010-07-07 21:40               ` utf-8' chars from Winxp machine may be problem related (was Re: xfs file system in process of becoming corrupt; though xfs_repair...) Linda A. Walsh
2010-07-07 23:40                 ` Stan Hoeppner
2010-07-08  0:38                   ` Linda A. Walsh
2010-06-30 18:25     ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Michael Monnerie
2010-06-30 23:30       ` rsync and corrupt inodes (was xfs_dump problem) Dave Chinner
2010-07-01  8:25         ` Michael Monnerie
2010-07-02  2:42           ` Dave Chinner
2010-07-02  6:21             ` Michael Monnerie
2010-07-04 22:53               ` Dave Chinner
2010-07-12 11:28                 ` Michael Monnerie
2010-07-07 21:56         ` Linda Walsh

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=4C2A92DA.1020202@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=mw@dermichi.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 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.