Bug 49
Summary: | Incorrect (?) error warnings | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | apeacock |
Component: | mount | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1998-11-20 12:10:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
apeacock
1998-11-12 01:55:22 UTC
Please show us the contents of your fstab file. /dev/hda3 / ext2 defaults 1 1 /dev/hda1 /dos/c vfat exec,dev,suid,rw,umask=000 0 0 /dev/hdc1 /dos/d vfat exec,dev,suid,rw,umask=000 0 0 /dev/hdc5 /dos/f vfat exec,dev,suid,rw,umask=000 0 0 /dev/cdrom /mnt/cdrom iso9660 user,noauto,ro #0 0 /dev/fd0 /mnt/floppy3.5 ext2 user,noauto #0 0 /dev/fd1 /mnt/floppy5.25 ext2 user,noauto /dev/hdc3 /data ext2 defaults 1 2 /dev/hdc4 /usr ext2 defaults 1 3 /dev/hdc2 none ignore 0 0 0 none /proc proc defaults /dev/hda2 none swap sw Op. I think I just found the problem. mount must not be parsing the file for comments correctly anymore. Hmm, that sounds like a relatively easy fix in the source code... For know, here is my solution. The lines that were: ----------------- /dev/cdrom /mnt/cdrom iso9660 user,noauto,ro # 0 0 /dev/fd0 /mnt/floppy3.5 ext2 user,noauto # 0 0 ----------------- become: ----------------- /dev/cdrom /mnt/cdrom iso9660 user,noauto,ro /dev/fd0 /mnt/floppy3.5 ext2 user,noauto ----------------- And my warnings disappear. assigned to Cristian There is also a line that has three zeros at the end, and that is an invalid line too. The parser in the new mount is far from perfect; however, this is what should be expected when the fstab is invalid. |