I'm afraid it's so long ago that I don't remember many details. I've
answered below as best I can...
On 12/17/06, Onno Benschop <email address hidden> wrote:
> Hi, thank you for your bug report.
>
> We've just been trying to reproduce this bug, but couldn't. Is there
> anything you can tell us about your computer that might give more
> information. For example:
>
> * Was a specific file, or group of files, involved?
It seemed to be a single file. That is, the fsck only complained
about that file, and I'm *pretty* sure that I only needed to delete
that one file to make the problem go away.
> * What names did affected files have?
It's listed in the original problem report.
> * Were they all in the same directory, what was the name of that directory?
Just one file. My *guess* is that it was in the root directory of
that partition, but that the partition was mounted somewhere like
"/mount/windows_f-drive/" or something like that.
> * How big was the partition that contained the files?
I don't remember - probably not super huge. This was just one of
several partitions residing on my 60 GB laptop hard drive. Almost
certainly smaller than 20 GB.
> * Which language was the file system?
I didn't realize they had languages. I've always told my OS installs
that I'm using American English.
> * Was the file of a particular size?
Don't remember. It wouldn't have been very small, because it was a
backup of a bunch of files. It was probably over 10 MB, and maybe
even a few GB in size. I don't remember.
> * Was the file a Windows .lnk file?
No.
> * What other symptoms did you notice?
None that I remember.
>
> We realise that we're asking lots of questions, but the bug you reported
> has potentially been identified as being part of a problem tucked away
> in the internal workings of the operating system and if that is the
> case, it may affect many users.
Hi guys,
I'm afraid it's so long ago that I don't remember many details. I've
answered below as best I can...
On 12/17/06, Onno Benschop <email address hidden> wrote:
> Hi, thank you for your bug report.
>
> We've just been trying to reproduce this bug, but couldn't. Is there
> anything you can tell us about your computer that might give more
> information. For example:
>
> * Was a specific file, or group of files, involved?
It seemed to be a single file. That is, the fsck only complained
about that file, and I'm *pretty* sure that I only needed to delete
that one file to make the problem go away.
> * What names did affected files have?
It's listed in the original problem report.
> * Were they all in the same directory, what was the name of that directory?
Just one file. My *guess* is that it was in the root directory of windows_ f-drive/ " or something like that.
that partition, but that the partition was mounted somewhere like
"/mount/
> * How big was the partition that contained the files?
I don't remember - probably not super huge. This was just one of
several partitions residing on my 60 GB laptop hard drive. Almost
certainly smaller than 20 GB.
> * Which language was the file system?
I didn't realize they had languages. I've always told my OS installs
that I'm using American English.
> * Was the file of a particular size?
Don't remember. It wouldn't have been very small, because it was a
backup of a bunch of files. It was probably over 10 MB, and maybe
even a few GB in size. I don't remember.
> * Was the file a Windows .lnk file?
No.
> * What other symptoms did you notice?
None that I remember.
>
> We realise that we're asking lots of questions, but the bug you reported
> has potentially been identified as being part of a problem tucked away
> in the internal workings of the operating system and if that is the
> case, it may affect many users.
No problem. Thanks for looking into it.
- Christian
> /launchpad. net/bugs/ 47215
> Thanks,
> Stefan and Onno
>
> --
> fsck.vfat hangs, eats CPU on problematic file
> https:/
>