| 2006-07-18 22:34:44 |
Jimmy P |
bug |
|
|
added bug |
| 2007-03-21 13:51:28 |
Ralph Janke |
coreutils: status |
Unconfirmed |
Needs Info |
|
| 2007-03-21 13:51:28 |
Ralph Janke |
coreutils: assignee |
|
rjanke |
|
| 2007-03-21 13:51:28 |
Ralph Janke |
coreutils: statusexplanation |
|
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 names for which this behaviour occurs.
Thanks, |
|
| 2007-04-07 02:22:44 |
Micah Cowan |
bug |
|
|
assigned to linux-source-2.6.20 (Ubuntu) |
| 2007-05-06 10:45:07 |
Ralph Janke |
coreutils: status |
Needs Info |
Confirmed |
|
| 2007-05-06 10:45:07 |
Ralph Janke |
coreutils: assignee |
txwikinger |
|
|
| 2007-05-06 10:45:07 |
Ralph Janke |
coreutils: statusexplanation |
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 names for which this behaviour occurs.
Thanks, |
|
|
| 2007-05-06 21:54:20 |
Micah Cowan |
coreutils: status |
Confirmed |
Needs Info |
|
| 2007-05-06 21:54:20 |
Micah Cowan |
coreutils: assignee |
|
micahcowan |
|
| 2007-05-06 21:54:20 |
Micah Cowan |
coreutils: statusexplanation |
|
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 the same problem ls -l: if you do, then it would definitely be evidence for a kernel, as opposed to a program, bug.
Could you please verify this for me? |
|
| 2007-05-07 18:06:23 |
Micah Cowan |
coreutils: status |
Needs Info |
Confirmed |
|
| 2007-05-07 18:06:23 |
Micah Cowan |
coreutils: assignee |
micahcowan |
|
|
| 2007-05-07 18:06:23 |
Micah Cowan |
coreutils: statusexplanation |
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 the same problem ls -l: if you do, then it would definitely be evidence for a kernel, as opposed to a program, bug.
Could you please verify this for me? |
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 conclusion strongly.
I'm going to set the coreutils bug back to Confirmed, out of respect for its previous setting; I'll also set the kernel bug the same. Hopefully, we'll be able to rule out one or the other, and reject it appropriately. |
|
| 2007-05-07 18:06:33 |
Micah Cowan |
linux-source-2.6.20: status |
Unconfirmed |
Confirmed |
|
| 2007-05-07 18:06:33 |
Micah Cowan |
linux-source-2.6.20: statusexplanation |
|
|
|
| 2007-05-16 19:04:46 |
Micah Cowan |
linux-source-2.6.20: status |
Confirmed |
Needs Info |
|
| 2007-05-16 19:04:46 |
Micah Cowan |
linux-source-2.6.20: importance |
Undecided |
Medium |
|
| 2007-05-16 19:04:46 |
Micah Cowan |
linux-source-2.6.20: statusexplanation |
|
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. |
|
| 2007-05-25 20:02:01 |
Micah Cowan |
linux-source-2.6.17: statusexplanation |
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. |
Setting back to 2.6.20, per feisty confirmation.
Have you run fsck on the vfat partition? |
|
| 2007-05-28 15:23:07 |
Micah Cowan |
linux-source-2.6.20: status |
Needs Info |
Confirmed |
|
| 2007-05-28 15:23:07 |
Micah Cowan |
linux-source-2.6.20: statusexplanation |
Setting back to 2.6.20, per feisty confirmation.
Have you run fsck on the vfat partition? |
|
|
| 2007-07-14 00:59:07 |
Jimmy P |
bug |
|
|
assigned to coreutils (Mandriva) |
| 2007-07-16 21:42:33 |
Brian Murray |
linux-source-2.6.20: assignee |
|
ubuntu-kernel-team |
|
| 2008-08-17 17:46:11 |
Andreas Moog |
coreutils: status |
Confirmed |
Fix Released |
|
| 2008-08-17 17:46:20 |
Andreas Moog |
linux: status |
Incomplete |
Fix Released |
|
| 2010-09-16 09:58:24 |
rusivi2 |
coreutils (Mandriva): status |
New |
Incomplete |
|
| 2010-09-16 14:58:10 |
C de-Avillez |
coreutils (Mandriva): status |
Incomplete |
New |
|
| 2010-09-16 14:58:13 |
C de-Avillez |
bug |
|
|
added subscriber C de-Avillez |
| 2010-09-16 14:58:34 |
C de-Avillez |
bug |
|
|
added subscriber rusivi1 |
