Jimmy P:
Thank you for your contribution to this bug. If you notice this is still
an issue in Mandriva, please post via their bugzilla:
https://qa.mandriva.com/ Thanks!
** Changed in: coreutils (Mandriva)
Status: New = Incomplete
--
du reports existing files as missing
@rusivi1: please do not touch tasks that are not Ubuntu.
** Changed in: coreutils (Mandriva)
Status: Incomplete = New
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: coreutils (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
seems to work fine in hardy. thanks!
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Since 8.04 is using coreutils 6.10, this bug appears to be gone for me.
Can the people that experienced the bug check again please? Maybe this
bug can be closed then (at least for Hardy and after that).
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received
For reference, here is some detailed information:
The underlying code that changed was in lib/fts.c.
- du, chmod, chown, chgrp, and the new chcon use fts.
- ls and cp use explicit recursion (and are therefore not affected)
--
du reports existing files as missing
I posted this problem to the coreutils mailing list and got a response.
The du from the current 6.9 version of coreutils is working nicely, so it
doesn't seem to be a kernel problem.
http://www.gnu.org/software/coreutils/
(Note: coreutils 6.9 won't compile directly, due to a more recent change
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
** Tags added: needs-devrelease-testing
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I installed mandriva 2007.1 on my machine and I get the same error.
coreutils-5.97-6mdv2007.1
** Also affects: coreutils (Mandriva)
Importance: Undecided
Status: New
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info = Confirmed
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
emmy:~$ sudo fsck.vfat /dev/sda2
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/sda2: 142476 files, 1155689/1186009 clusters
That is all the output that fsck gives. I am guessing that means the
filesystem is ok?
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You
I get the same problem on feisty:
emmy:/media/sda2$ du --max-depth=1
641440 ./i386
10880 ./valueadd
40768 ./dotnetfx
3008./book
224 ./sysinfo
3778080 ./windows
2097088 ./Documents and Settings
4787328 ./Program Files
du: `./System Volume Information': No such file or directory
du:
Setting back to 2.6.20, per feisty confirmation.
Have you run fsck on the vfat partition?
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: linux-source-2.6.17 = linux-source-2.6.20
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug
Changing the linux source version to 2.6.17, as AFAICT it has not yet
been reproduced on feisty.
Has fsck been run on the partition that is producing problems?
Also: are you using an ext2fs driver in windows that includes write
support? I have had mild corruption issues from such things, myself.
A couple observations:
1) When du can't find a directory, going into that directory and executing a du
or an ls causes subsequent invocations of du to find that directory
2) ls -l seems pretty normal
evidence:
cindy:/windows$ du --max-depth=1
19456 ./backup
.
.
1120./car
du: `./Media': No
Hm, while not what I was expecting to see, it still looks much more like
a driver/disk problem than du's... but now I'm curious what could make
du fail like that, while ls -l doesn't.
Also, the fact that looking at ext2fs/ with ls -l fixes du's ability
to se ext2fs seems to support this
** Changed in: coreutils (Ubuntu)
Assignee: Ralph Janke = (unassigned)
Status: Needs Info = Confirmed
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Well, but it still sounds like a likely kernel issue, to me, if the
deciding factor is whether or not it's mounted in utf-8 mode.
I have seen very similar issues on corrupted filesystems, when ls works
but ls -l doesn't (readdir() returns the name, but stat() can't find
it). I suspect you'd have
Er, obviously I misread how much of a deciding factor utf8 is; however,
I'd still be interested in seeing what the success is like with ls -l.
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs,
Does cifs use vfat? It happens also with cifs mounts
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This sounds to be a vfat driver issue rather than a du issue; I've added
the linux kernel package for this bug.
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
du reports existing files as missing
https://bugs.launchpad.net/bugs/53388
You
this is on edgy -
mount |grep windows:
/dev/hda1 on /windows type vfat (rw,umask=007,gid=46,utf8)
cindy:/windows$ du --max-depth=1
19456 ./backup
465088 ./i386
50560 ./dell
23296 ./discover
2077312 ./winnt
15136 ./recycled
22112 ./drivers
1376./mb
970912 ./Documents and Settings
I can confirm and reproduce this behaviour on dapper if unregular
characters are part of the file name (i.e. a telephone symbol from
wingdings font).
--
du reports existing files as missing
https://launchpad.net/bugs/53388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have found a similar behaviour using du on a cifs from Windows
mounted directory, although only with files that contain spaces in their
file names.
On ext3 filesystem I had no problems with such files.
Can you give some more information about the filesystem, mounting, as
well the kind of file
Could you also test if this happens when you mount the drive without
UTF8 as an option.
--
du reports existing files as missing
https://launchpad.net/bugs/53388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I get the same behavior on edgy on a different machine.
--
du reports existing files as missing
https://launchpad.net/bugs/53388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
sorry for the spam, this is on ubuntu 6.06
--
du reports existing files as missing
https://launchpad.net/bugs/53388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
27 matches
Mail list logo
