On Tuesday 28 October 2014 at 06:41:32, Andrei Borzenkov wrote:
В Mon, 27 Oct 2014 14:10:47 -0700
Chris Leech cle...@redhat.com пишет:
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
В Sun, 09 Nov 2014 20:15:56 +0300
Ivan Shapovalov intelfx...@gmail.com пишет:
On Tuesday 28 October 2014 at 06:41:32, Andrei Borzenkov wrote:
В Mon, 27 Oct 2014 14:10:47 -0700
Chris Leech cle...@redhat.com пишет:
At boot fstab-generator is picking up on the _netdev option in
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 of
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
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 remote block
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 the time
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 are
On Tue, Oct 28, 2014 at 06:41:32AM +0300, Andrei Borzenkov wrote:
В Mon, 27 Oct 2014 14:10:47 -0700
Chris Leech cle...@redhat.com пишет:
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
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.
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
В Fri, 31 Oct 2014 01:53:26 +0100
Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl пишет:
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:
В Thu, 30 Oct 2014 15:15:03 -0700
Chris Leech cle...@redhat.com пишет:
On Tue, Oct 28, 2014 at 06:41:32AM +0300, Andrei Borzenkov wrote:
В Mon, 27 Oct 2014 14:10:47 -0700
Chris Leech cle...@redhat.com пишет:
But there are two cases that are problematic, adding entries to fstab at
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
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
14 matches
Mail list logo
