Bug 198626 - Mounted USB key with FAT32 file-system, inserted 2nd key, mounted file-system went blank
Summary: Mounted USB key with FAT32 file-system, inserted 2nd key, mounted file-system...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-fs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-16 14:40 UTC by donaldcallen
Modified: 2015-03-17 14:19 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description donaldcallen 2015-03-16 14:40:11 UTC 
I inserted a USB key with a FAT32 file-system on its one and only partition and mounted it on a newly created directory in /tmp. After mounting, I did an ls to verify that what I expected to be there was there, and it was. Among the contents was a .iso file that needed to be copied to another USB key. I inserted that key and began typing the dd command to do the copy, while cd-ed to the directory where I'd mounted the first key. When I hit 'tab' to complete the name of the .iso file, it would not complete. So I backed out, did another ls and got nothing! No files! But the file-system was still mounted, confirmed with df. I suspect that the insertion of the second USB key confused the system somehow and it lost track of the first.
Comment 1 donaldcallen 2015-03-16 15:23:05 UTC 
I should mention that I did try to reproduce this and have not been successful thus far.

The key in question is a Sandisk Cruzer Facet, 8GB
Comment 2 donaldcallen 2015-03-16 15:24:47 UTC 
The second key, the key to which I wanted to do the copy, was a Kingston DTSE9,  8GB.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2015-03-17 14:19:23 UTC 
Unsure about where the error lies, but assume that it's in msdosfs.