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.
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.