Red Hat Bugzilla – Bug 185534
[EMC RHEL3 U8 bug] init:mount:fsck fails when fstype is set to auto on _netdev device in /etc/fstab
Last modified: 2015-01-07 19:12:29 EST
Description of problem:
With the following entry in /etc/fstab I see an error message from
init:mount:fsck: "Could not determine filesystem type for /dev/emcpowera1" and
init:netfs:fsck is successful.
/dev/emcpowera1 /zoner/emcpowera auto _netdev 1 1
If I change the entry in /etc/fstab to the following there are no error
messages from init:netfs:fsck and init:netfs:fsck is successful.
/dev/emcpowera1 /zoner/emcpowera ext2 _netdev 1 1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Place entry "/dev/emcpowera1 /zoner/emcpowera auto _netdev 1 1" into
2. Reboot server
Error message in /var/log/messages whem mount() performs fsck - "Could not
determine filesystem type for /dev/emcpowera1"
mount:fsck should not attempt a _netdev device at this time. It seems to do it
because the fstype is auto. If I change it to ext2, it will ignore the device
because of the _netdev option. Parsing for auto should also include option
_netdev in the logic so this error does not occur.
Reference BZ #169403
This is really a fsck bug. The fsck command always tries to determine real
filesystem type before fs_opts checks. I think it's bad logic. There should be
fs_opts test __before__ fs_type tests.
Wayne, this needs an issue tracker, with reference to this bugzilla. So far this
has not been on anyone's radar at RH for inclusion into an Update.
Wayne, you're right that fsck tries open the device, but the message "Could not
determine filesystem type" is from RHEL3 fsck.
Changing RHEL4 -> RHEL3.
My bad. You are correct. I was hastily creating this BZ as an update to the
previous BZ. It is a RHEL 3.0 bug. If I see the same issue in RHEL 4.0 I'll
generate a seperate BZ.
This issue is on Red Hat Engineering's list of planned work items
for the upcoming Red Hat Enterprise Linux 3.8 release. Engineering
resources have been assigned and barring unforeseen circumstances, Red
Hat intends to include this item in the 3.8 release.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.