2010-05-21 02:42:33 Issue in mounting sdiw1 in USB memory stick
John Peter (INDIA)
I have enabled USB hotplug in the kernel. Now in my application I am continuously attaching and detaching two USB sticks, one with FAT file system and the other with NTFS file system.
From the kernel it is assigned partitions like
In this sequence, when I reach sdiw1, I am not able to mount the USB stick for sdiw1 with ntfs file system (mount -t ntfs /dev/sdiw1 /mnt ) while I can mount it for all the previous sdaa,sdbb etc. Can any one please clarify regarding this?
2010-05-21 03:43:49 Re: Issue in mounting sdiw1 in USB memory stick
Mike Frysinger (UNITED STATES)
probably the dev_t limit (256). but you already know that this behavior is incorrect since you asked a similar question before. new devices should be sda once sda has been removed. figure out why that isnt working and the 256 limit wont matter.
2010-05-21 10:57:17 Re: Issue in mounting sdiw1 in USB memory stick
Amol Sukerkar (UNITED STATES)
When I encountered this problem, there was a DEVNUM_ROUND_ROBIN defined in USB core(usb.c). This would increment the mount point every time a USB mass storage device would be plugged in. I undefined that and that stopped incrementing. I thought this is similar to what Mike described earlier.
Also, in my "antique" kernel 2.4 back then, it would somehow keep track of GUID and device filename together. If the new device plugged in did not match the GUID, it would automatically increment the device file, lets say, to sdb even though sda wasn't in use. It was a nightmare fixing that.
However, the first thing I would look at is whether the device file sdiw1 is present in your /dev directory. If not, then you will never be able to mount your mass storage device.
Hope this is useful.