public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: Dave Chinner <david@fromorbit.com>
Cc: 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, 06 Jul 2010 22:56:34 -0700	[thread overview]
Message-ID: <4C341712.5030202@tlinx.org> (raw)
In-Reply-To: <4C33F20F.4040905@tlinx.org>

For what it's worth, my 'undeletable' files give every appearance of
being 'plain' UTF-8 encoded file names.  Wrote a perl script that looped
through and used the 'bytes' pragma to look at the bytes.  Looks like
valid UTF-8.  Also had it try to remove the files.  Didn't work.



Read 9 files
 1: 2e                                                >|.               |<
 2: 2e 2e                                             >|..              |<
 3: 42 6f 72 64 75 72 65 20  70 6f 69 6e 74 69 6c 6c  >|Bordure pointill|<
    c3 a9 65 20 2d 20 42 6c  61 6e 63 2d 6e 6f 69 72  >|..e - Blanc-noir|<

Unlink of "Bordure pointillée - Blanc-noir" failed: No such file or directory

 4: 42 6f 72 64 75 72 65 20  70 6f 69 6e 74 69 6c 6c  >|Bordure pointill|<
    c3 a9 65 20 2d 20 4e 6f  69 72 2d 62 6c 61 6e 63  >|..e - Noir-blanc|<

Unlink of "Bordure pointillée - Noir-blanc" failed: No such file or directory

 5: 43 61 64 72 65 20 63 65  6e 74 72 c3 a9 20 31 20  >|Cadre centr.. 1 |<
    2d 20 42 61 73 65                                 >|- Base          |<

Unlink of "Cadre centré 1 - Base" failed: No such file or directory
....rest of output truncated.

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

  reply	other threads:[~2010-07-07  5:53 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         ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30  1:16           ` 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 [this message]
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=4C341712.5030202@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=david@fromorbit.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