Maximiliano Curia wrote, on 05/12/11 21:57:
Hola Arthur Marsh!
El 05/12/2011 a las 12:48 escribiste:
Is there a standard set of error values that mount.$fstype is
supposed to return to mount? The original problem was the boot
process failing if a vfat filesystem was listed in /etc/fstab but
the device did not exist (e.g. a removable drive not plugged in).
The normal 0 on success and a != 0 on failure is good enough for the mount
command.
I'm not sure I follow the use case. I added a line to my fstab to mount my
pendrive as:
/dev/sdb1 /mnt vfat defaults 0 0
I removed my pendrive and rebooted my computer. It booted normally, the system
tried to mount the pendrive, failed, and continued the with rest of the
filesystems.
Is this the use case you were mentioning?
Yes, I think so... although I mounted by UUID
It might have been that with dosfstools installed, fsck.vfat is always
run before mount and if errors were found but fixed, the error code made
the boot process halt rather than continue.
I found some workaround or the problem was fixed, but maybe some
pointers to documenting the error codes that mount expects from
mount.$fstype could be helpful.
The "appropriate" value should be the ones listed in the mount man page.
Should we close this bug?
I'm not sure how to create a vfat filesystem that fsck.vfat finds errors
and fixes, so it's not easy for me to reproduce.
Feel free to close it, but if a fsck finds and fixes errors, I believe
that the boot process should continue.
Thanks for reporting,
Thanks for responding!
Arthur.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
