[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#421151: marked as done (linux-image-2.6.18-4-686: reads the same inode twice)



Your message dated Fri, 9 Oct 2009 22:08:24 +0200
with message-id <20091009200824.GA12197@galadriel.inutil.org>
and subject line Re: linux-image-2.6.18-4-686: reads the same inode twice
has caused the Debian Bug report #421151,
regarding linux-image-2.6.18-4-686: reads the same inode twice
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
421151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421151
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Severity: minor

Just want to let you know Linux can say things like
$ ls -ogi|grep xls
3354 -rw-r--r-- 1  142848 2007-04-09 14:06 ??????.xls
3354 -rw-r--r-- 1  142848 2007-04-09 14:06 ??????.xls

It is stuck on the first inode just because of a character set issue!

$ mount -t vfat -o iocharset=cp950 ...; ls -ogi|grep xls
3935 -rw-r--r-- 1  142848 2007-04-09 14:06 西部幹線下行.xls
3936 -rw-r--r-- 1  138240 2007-04-09 14:07 西部幹線上行.xls

Saying "??????" is OK, but don't read the same inode twice!

Apparently the files must be created on Windows and viewed on Linux to
cause the error. I could not reproduce it with files created on Linux.

Please reassign this bug if not the right package.


--- End Message ---
--- Begin Message ---
On Sat, Oct 03, 2009 at 09:40:15AM +0800, jidanni@jidanni.org wrote:
> >>>>> "MM" == Moritz Muehlenhoff <jmm@inutil.org> writes:
> MM> Can you reproduce this on a more recent Linux kernel?
> I don't know. I suppose I should have included a exact test case, but
> that would have been very complicated. So I thought somebody would know
> at a glance...

Closing, since it's not reprocible and against an old kernel, if
there were a general problem we'd have encountered it more often.

Cheers,
        Moritz


--- End Message ---

Reply to: