- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Base OS
- Operating System All
- Severity Low
- Reported Version SuperZaxxon Beta 4
Attached to Project: OpenPandora Main OS
Opened by laurens simonis - 27.05.2010
Last edited by Michael Mrozek - 23.06.2010
Opened by laurens simonis - 27.05.2010
Last edited by Michael Mrozek - 23.06.2010
FS#83 - getting more /media/mmcblk?p1
From a conversation with skeezix:
I'm seeing /media/mmcblk0p1, mmcblk1p1, mmcblk2p1, mmcblk3p1 and mmcblk4p1 - is that something I should worry about? This started after I inserted & ejected my sd card a couple of times.
To which skeezix said:
The system starts at /media/mmcblk0 (with p1 ec being the partition number); if you eject the SD, then stick it back in, it will try to go to the earlier number again, but if some process was watching that SD when you ejected it, the system will nto be able to recycle that number, so you get the next blk number. So if you end up with /media/mmcblk5p1 (say), then it means you've been eject/inserting, and some program or another has been watching the SD instead of letting it go.
Isn't it nicer to cleanup the ones above 1 (so 0 and 1 are there) at startup to avoid confusion?
Closed by Michael Mrozek
23.06.2010 20:54
Reason for closing: Fixed
Additional comments about closing: Basically fixed with upcoming Hotfix 3, which uses label names and seems to properly unmount and remove directories.
23.06.2010 20:54
Reason for closing: Fixed
Additional comments about closing: Basically fixed with upcoming Hotfix 3, which uses label names and seems to properly unmount and remove directories.