Bug 98202
Summary: | after nautilus, mount of floppy with device name gives error when mount succeeds | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Don Himelrick <dch> | ||||
Component: | util-linux | Assignee: | Elliot Lee <sopwith> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 9 | CC: | alexl | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-08-20 18:42:09 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Don Himelrick
2003-06-27 21:41:50 UTC
Created attachment 92660 [details]
strace of mount after using nautilus
This is an strace of "mount /dev/fd0" after using nautilus to mount and umount
a floppy disk. I don't know why, but the mount doesn't succeed when doing the
strace. The strace does have some "invalid argument" errors in it though.
Yuk. An obscure bug that sounds real & reproducible. Alex, any ideas from the nautilus side? Wow. bizarre bug. The reason it fails under strace is (i think) that the whole setuid thing doesn't work for straced processes. You'd have to test it as root with strace (but then the problem goes away!). Upfront i have no idea what is causing it. It needs some further study. Sighted with FC3 devel tree. What happens is that mount tries to guess the fstype, but it's a bad floppy so you see that I/O error message. However, the mount itself still succeeds. The problem happens for me with both 'mount /dev/fd0' and 'mount /mnt/floppy' - I'm guessing in your case it was just the timing of commands rather than the exact command line itself. Anyways, use a good floppy and the problem goes away. |