Bug 163661
Summary: | Default automount for CF cards in PCMCIA is very, very slow | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew D. Stadler <stadler> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | davej, wtogami |
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: | 2005-08-30 10:55:38 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: |
Description
Andrew D. Stadler
2005-07-20 01:39:48 UTC
For various reasons, ext2 will be slower here. I'm slightly surprised at the size of the difference, but only slightly. ext2 has much more metadata to maintain on the disk than fat --- it maintains group descriptors, the superblock, the inode, indirect blocks and bitmaps for every write; and to keep the fs completely consistent on disk, it _has_ to update all of these after every write for a sync mount. That's a lot of metadata, and it's not "fixable" because it's not a bug --- it's just a design property that makes ext2 suboptimal for sync CF mounts. This isn't something that's going to get any Red Hat engineering attention for ext2. And I'm not sure that the automounter should get "fixed", either --- it is dangerous to have non-sync as a default mount option for removable media, as users who remove the media early can lose data. The best recommendation I can really give right now is that ext2 is inappropriate if you're going to rely on automount's default behaviour; either use FAT or explicitly choose non-sync mount. If you want to debate whether non-sync should be the default for this case, please feel free to reopen the bug and we can reassign it to the appropriate non-kernel component. |