Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-11-09 Thread Andrei Borzenkov
В Sun, 09 Nov 2014 20:15:56 +0300 Ivan Shapovalov пишет: > On Tuesday 28 October 2014 at 06:41:32, Andrei Borzenkov wrote: > > В Mon, 27 Oct 2014 14:10:47 -0700 > > Chris Leech пишет: > > > > > > > > At boot fstab-generator is picking up on the _netdev option in fstab, > > > and the gen

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-11-09 Thread Ivan Shapovalov
On Tuesday 28 October 2014 at 06:41:32, Andrei Borzenkov wrote: > В Mon, 27 Oct 2014 14:10:47 -0700 > Chris Leech пишет: > > > > > At boot fstab-generator is picking up on the _netdev option in fstab, > > and the generated mount units are ordered against remote-fs properly. > > If I leave a fil

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-11-07 Thread Karel Zak
On Thu, Nov 06, 2014 at 09:10:51PM -0800, Chris Leech wrote: > > Not sure, maybe it's possible to detect this by scsi info in /sys. > > I took a look at what lsscsi is doing to guess at transport type. iSCSI > is kind of ugly, FCoE is really ugly, and for both of those there exists > a variety o

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-11-06 Thread Chris Leech
On Fri, Oct 31, 2014 at 09:32:57AM +0100, Karel Zak wrote: > It would be really better to have within systemd a generic function > is_net_blkdev() than rely on external fragile configuration. I have > doubts that anyone uses -o _netdev on command line when manually > mounts filesystem. The one

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-31 Thread Karel Zak
On Thu, Oct 30, 2014 at 03:04:59PM -0700, Chris Leech wrote: > On Thu, Oct 30, 2014 at 12:10:16PM +0100, Karel Zak wrote: > > On Tue, Oct 28, 2014 at 02:29:35AM +0100, Lennart Poettering wrote: > > > On Mon, 27.10.14 14:10, Chris Leech (cle...@redhat.com) wrote: > > > > > > > So for any mounts to

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Andrei Borzenkov
В Thu, 30 Oct 2014 15:15:03 -0700 Chris Leech пишет: > On Tue, Oct 28, 2014 at 06:41:32AM +0300, Andrei Borzenkov wrote: > > В Mon, 27 Oct 2014 14:10:47 -0700 > > Chris Leech пишет: > > > > > > But there are two cases that are problematic, adding entries to fstab at > > > runtime and manually m

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Andrei Borzenkov
В Fri, 31 Oct 2014 01:53:26 +0100 Zbigniew Jędrzejewski-Szmek пишет: > On Thu, Oct 30, 2014 at 03:09:25PM -0700, Chris Leech wrote: > > On Tue, Oct 28, 2014 at 01:57:06AM +0100, Zbigniew Jędrzejewski-Szmek wrote: > > > On Mon, Oct 27, 2014 at 02:10:47PM -0700, Chris Leech wrote: > > > > ... > > >

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Oct 30, 2014 at 03:09:25PM -0700, Chris Leech wrote: > On Tue, Oct 28, 2014 at 01:57:06AM +0100, Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, Oct 27, 2014 at 02:10:47PM -0700, Chris Leech wrote: > > > ... > > > If there's no matching mount unit from fstab-generator, one gets created > > >

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Chris Leech
On Tue, Oct 28, 2014 at 01:57:06AM +0100, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Oct 27, 2014 at 02:10:47PM -0700, Chris Leech wrote: > > ... > > If there's no matching mount unit from fstab-generator, one gets created > > dynamically when the fs is mounted by monitoring /proc/self/mountinfo.

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Chris Leech
On Tue, Oct 28, 2014 at 06:41:32AM +0300, Andrei Borzenkov wrote: > В Mon, 27 Oct 2014 14:10:47 -0700 > Chris Leech пишет: > > > > But there are two cases that are problematic, adding entries to fstab at > > runtime and manually mounting without adding to fstab (while still using > > the _netdev

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Chris Leech
On Thu, Oct 30, 2014 at 12:10:16PM +0100, Karel Zak wrote: > On Tue, Oct 28, 2014 at 02:29:35AM +0100, Lennart Poettering wrote: > > On Mon, 27.10.14 14:10, Chris Leech (cle...@redhat.com) wrote: > > > > > So for any mounts to remote block devices (unlike remote file system > > > protocols which a

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-30 Thread Karel Zak
On Tue, Oct 28, 2014 at 02:29:35AM +0100, Lennart Poettering wrote: > On Mon, 27.10.14 14:10, Chris Leech (cle...@redhat.com) wrote: > > > So for any mounts to remote block devices (unlike remote file system > > protocols which are detected by the fs name), unless there is an fstab > > entry at th

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-27 Thread Andrei Borzenkov
В Mon, 27 Oct 2014 14:10:47 -0700 Chris Leech пишет: > > At boot fstab-generator is picking up on the _netdev option in fstab, > and the generated mount units are ordered against remote-fs properly. > If I leave a filesystem mounted at shutdown, it will be unmounted before > the iSCSI session is

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-27 Thread Lennart Poettering
On Mon, 27.10.14 14:10, Chris Leech (cle...@redhat.com) wrote: > So for any mounts to remote block devices (unlike remote file system > protocols which are detected by the fs name), unless there is an fstab > entry at the time fstab-generator is run they get treated like local fs > mounts and conn

Re: [systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-27 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Oct 27, 2014 at 02:10:47PM -0700, Chris Leech wrote: > Hi, I was hoping someone could help me make sure I'm not overlooking > something with trying to manage mounts on iSCSI disks. > > I have an iscsi.service which starts and stops sessions to iSCSI > targets. It's set with Before=remote-

[systemd-devel] remote-fs ordering, iSCSI and _netdev

2014-10-27 Thread Chris Leech
Hi, I was hoping someone could help me make sure I'm not overlooking something with trying to manage mounts on iSCSI disks. I have an iscsi.service which starts and stops sessions to iSCSI targets. It's set with Before=remote-fs-pre.target and Wants=remote-fs-pre.target to ensure that remote fs o