(This is a mass-update to all current FC6 kernel bugs in NEW state)
Hello,
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
http://fedoraproject.org/wiki/KernelBugTriage
I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!

ok, this is still {t}here in f8 but, i've found out there are two different
copies of the FAT so i supose mounting it read only is the sane thing to do.
what may be considered a bug is that the user is not informed _why_ the
filesystem is mounted read only ....

Hmm....I'll change the version to F8, but this looks like filesystem corruption
or non-conformance to me - hence it's not 'safe' to mount it rw. I'd be
interested in what an fsck (I think there's one for vfat) would do to this, with
the caveat that it could render the device unusable :(

as i've said, fsck -t vfat shows there are two different copies of the FAT, so
indeed it's not safe to mount it rw. unfortunately i don't have the device
available to paste the exact output. still, it would have been nice to tell the
user __why__ it was mounted read only (or at least to let him know that this
happened), in current config, the device is just mounted.

(In reply to comment #9)
> as i've said, fsck -t vfat shows there are two different copies of the FAT, so
> indeed it's not safe to mount it rw. unfortunately i don't have the device
> available to paste the exact output. still, it would have been nice to tell the
> user __why__ it was mounted read only (or at least to let him know that this
> happened), in current config, the device is just mounted.
This is the job of dmesg, namely:
Jan 5 10:11:44 obi kernel: FAT: Filesystem panic (dev sdc1)
Jan 5 10:11:44 obi kernel: fat_get_cluster: invalid cluster chain (i_pos 0)
Jan 5 10:11:44 obi kernel: File system has been set read-only
I guess you're asking for a window pop-up of some kind if you're running in X?
If so I'd be happy to change the bug subject as an RFE as per:
http://fedoraproject.org/wiki/BugsAndFeatureRequests
Cheers
Chris

Ok,
I had the exactly same problem with WD Password 120GB External HDD, it was
formatted with fat32, once I just didn't umount it, and just pulled it out. Same
problems as you're saying, its filesystem would panic and it would report
read-only.
HOWEVER, on Windows it would act normally. I first thought it was something due
to permissions or something, but after I tried everything, and just before
formatting my hdd all over again.
BUT, that filesystem panic, gave me an idea.
I fired up my virtual windows over vmware, selected to check for errors on that
same disk and selected to automatically fix all the errors. It took few hours,
but after it, it all simply worked!
This may not be solution to your problem, but in my case it simply worked!

Not sure what to do with this bug. The kernel *does* inform the user that the
device is mounted read-only, via it's normal messaging systems (dmesg and
syslog). If you'd like something in X to say so, I'm not even remotely sure
where to file this, I can check with some folks though. Or can this just be closed?

(In reply to comment #0)
> Description of problem:
>
> When I plug my iAudio X5 (portable media player) into the USB port, there is a
> filesystem panic and the filesystem is mounted as read-only. I can not delete
> or create files on the device (which renders it pretty useless).
>
What tool are you using to create/delete files?
If it is nautilus then it should be able to tell that the filesystem is mounted
read-only...

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.

Note

You need to
log in
before you can comment on or make changes to this bug.