FS#17887 - [initscripts] Add ",noopts=_netdev" to the NETFS list in /etc/rc.sysinit

Attached to Project: Arch Linux
Opened by Yannick Loth (yannick555) - Monday, 18 January 2010, 13:14 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 19 May 2010, 16:01 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Roman Kyrylych (Romashka)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When using iscsi (with the package open-iscsi, from AUR), at start, the filesystem checks fail (as the device is not accessible through iscsi as long as open-iscsi is not started...) if the iscsi-device is defined in /etc/fstab.

Adding ",noopts=_netdev" to the NETFS list in /etc/rc.sysinit implies that fsck won't check filesystems of devices with the _netdev option set.

This solution works for me...

NB: I think this is an issue with every type of networked filesystem device and as such is not specific to iscsi or the open-iscsi package!

Additional info:
* package version(s)
2.0.871.2-1
* config and/or log files etc.
my NETFS list: NETFS="nonfs,nonfs4,nosmbfs,nocifs,nocodafs,noncpfs,nosysfs,noshfs,nofuse,nofuseblk,noglusterfs,noopts=_netdev"

Steps to reproduce:
Use Archlinux as an iscsi-initiator with open-iscsi, add the remote iscsi-device in fstab for automatic mounting at boot and reboot.
During boot-filesystem-checks, the error should show up.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 19 May 2010, 16:01 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see comments
Comment by Yannick Loth (yannick555) - Monday, 18 January 2010, 13:16 GMT
NB: I think this is an issue with every type of networked filesystem device and as such is not specific to iscsi or the open-iscsi package!

That's why I didn't put the bug report in AUR bugs...
Comment by Aaron Griffin (phrakture) - Monday, 18 January 2010, 23:24 GMT
Any issues with adding this?
Comment by Roman Kyrylych (Romashka) - Wednesday, 03 March 2010, 08:53 GMT
After implementing  FS#11437  we have this code:
/bin/mount -a -t $NETFS -O no_netdev
Shouldn't that do exactly the same thing?
(BTW, man mount is silent about noopts)
Comment by Roman Kyrylych (Romashka) - Wednesday, 03 March 2010, 09:02 GMT
Doh, it was about fsck. I should sleep more. :-/
Still, I see an issue:
since noopts is for fsck it should not be passed to mount,
so it is better to add noopts=_netdev explicitly to the fsck line instead of putting it in $NETFS
Comment by Dan McGee (toofishes) - Friday, 07 May 2010, 13:55 GMT
This seems fine to me; I'm surprised we don't have the patch attached here yet from someone. Easy pickings.
Comment by Yannick Loth (yannick555) - Tuesday, 18 May 2010, 15:51 GMT
After a recent "pacman -Syu", the issue arose again... The OS tried to fsck the remote iscsi disk, and it couldn't.

Is it finally possible to disable fsck from checking iscsi disks at boot, and to put the solution in the right package, so that an update doesn't break systems which use iscsi?

Thanks
Comment by Dan McGee (toofishes) - Tuesday, 18 May 2010, 16:03 GMT Comment by Thomas Bächler (brain0) - Tuesday, 18 May 2010, 16:29 GMT
I don't get it. This is not a bug, it's an error in your configuration. In fstab, you specify whether to check your filesystems in the last 2 columns. If you told your system to perform a file system check, then you can't blame it for doing so.
Comment by Yannick Loth (yannick555) - Tuesday, 18 May 2010, 17:09 GMT
Oh fine, my apologies.

I completely ignored this fact.

Loading...