lkml.org 
[lkml]   [2007]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: it seems at XFS bug?!
On Sat, May 19, 2007 at 09:14:10PM +0200, Bernd Eckenfels wrote:
> In article <6101e8c40705191117h40c8af70sfc9d0617a99a248b@mail.gmail.com> you wrote:
> > 0000500 8 6 1 2 5 4 9 - r w - r - - r
> > 3638 3231 3435 2039 722d 2d77 2d72 722d
> > 0000520 - - 1 r o o t r o o t
> > 2d2d 3120 7220 6f6f 2074 6f72 746f 2020
> > 0000540 0 2 0 0 7 - 0 5 - 0 6
> > 2020 2020 2030 3032 3730 302d 2d35 3630
> > 0000560 1 2 : 4 1 \n \0
> > 3120 3a32 3134 a020 000a
> > 0000571
>
> That file with the inode 8612549 has indeed an empty name. (And I wonder a
> bit about the trailing \0, my ls does not do that?)

No, look closer above, its name is the single-character '\xa0'. It's
this output format which makes the analysis difficult. And it's also
'od' which has added '\0' to pad its 16 bit buffer. I tend to prefer
to use 'od -tx1' or 'od -ctx1' here.

I would suggest doing 'rm -i ?' to remove that file, or rm -i $'\xa0'
for the paranoid.

Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-05-19 21:23    [W:0.051 / U:0.616 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site