LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   kernel programming error...cannot see usb label (https://www.linuxquestions.org/questions/linux-software-2/kernel-programming-error-cannot-see-usb-label-387079/)

Yerp 11-27-2005 05:17 PM

mount error...cannot see usb label
 
Okay, I have been dealing with this problem for some time now.
Here are my end results of research and testing:

1) mkdosfs -n some11characterlabel /dev/sda1
2) /dev/sda1 = Flash Voyager 512mb usb memory stick, 100mb vfat partition
3) Using kernels 2.6.14 and 2.6.13.* I am unable to see filesystem labels for fat16 partitions, possibly all vfats (8,12,32..). mount -l, shows no label. I cannot mount the devices by LABEL=some11characterlabel
4) kernels 2.6.11 and earlier have no problems (2.6.12 not tested) reading the vfat filesystem labels or mounting by LABEL
5) Moving the disk to a windows system shows the given label with no problems.
6) My goal is to be able to have /etc/fstab mount the usb-stick based on a LABEL so that I can have multiple scsi devices and have the correct one mounted irregardless of how the scsi devices are loaded.
7) I prefer to use the latest kernels...but I am willing to change to a usb-label stable version..unless that version gives me problems with other priorities..

So, here are my questions.
1) Has this already been noticed? If so, where can I find information on this bug (I have searched rather unsuccessfully thus far..)
2) Any clues what else may be causing this. I have tested this on many different systems and the only cause seems to be what kernel version I am running. (>= 2.6.13.* = failure)
3) Who should I talk to about this problem. As I don't have any specifics of where the problem is other than the generic kernel numbers, I cannot see myself mailing this to www.kernel.org..
4) Anything else I should know?

EDIT:
I have forgotten to test one important aspect, I booted to a completely different machine with a 2.6.11 kernel and chrooted to my problematic one. It seems after mounting proc I still cannot see, so I changed the thread name accordingly.
I still intend to test a 2.6.14 kernel on a different system just to make sure.

EDIT:
it seems that the error appeared again in the 2.6.11.12 kernel on the completely different system.


All times are GMT -5. The time now is 06:16 AM.