All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bug fixes for 4.2-rc2
Date: Sat, 11 Jul 2015 14:07:10 +0200	[thread overview]
Message-ID: <55A106EE.3050204@web.de> (raw)
In-Reply-To: <20150705215312.GE8628@thunk.org>

Theodore Ts'o wrote on 07/05/2015 23:53:
> The following changes since commit a2fd66d069d86d793e9d39d4079b96f46d13f237:
> 
>   ext4: set lazytime on remount if MS_LAZYTIME is set by mount (2015-06-23 11:03:54 -0400)
> 
<snip>

Hi Ted,

I'm testing this patch and "ext4: set lazytime on remount if MS_LAZYTIME is set
by mount" on top of stable kernel 4.1.2.

So far no problems with lazytime enabled. Thanks for that :-)

But remounting with mount version 2.26.2 sucks. As promised, lazytime can be
enabled. But disabling it or trying to switch between atime, relatime, and
noatime doesn't work.

Starting from

# grep sda /proc/mounts
/dev/sda2 /home ext4 rw,lazytime,noatime,nobarrier,errors=remount-ro 0 0

some strace output:

# strace -o /tmp/st mount -o remount,nolazytime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x2152780, MS_MGC_VAL|MS_REMOUNT|MS_NOATIME,
"nobarrier,errors=remount-ro") = 0

# strace -o /tmp/st mount -o remount,relatime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x1543780, MS_REMOUNT|MS_RELATIME|MS_NOATIME,
"nobarrier,errors=remount-ro") = 0

# strace -o /tmp/st mount -o remount,atime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x1534780, MS_MGC_VAL|MS_REMOUNT,
"nobarrier,errors=remount-ro") = 0

The contents of /proc/mounts isn't changed by all this :-(

Or should I contact the util-linux developers?

-- 
Regards,
Jörg.


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: "Theodore Ts'o" <tytso@mit.edu>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bug fixes for 4.2-rc2
Date: Sat, 11 Jul 2015 14:07:10 +0200	[thread overview]
Message-ID: <55A106EE.3050204@web.de> (raw)
In-Reply-To: <20150705215312.GE8628@thunk.org>

Theodore Ts'o wrote on 07/05/2015 23:53:
> The following changes since commit a2fd66d069d86d793e9d39d4079b96f46d13f237:
> 
>   ext4: set lazytime on remount if MS_LAZYTIME is set by mount (2015-06-23 11:03:54 -0400)
> 
<snip>

Hi Ted,

I'm testing this patch and "ext4: set lazytime on remount if MS_LAZYTIME is set
by mount" on top of stable kernel 4.1.2.

So far no problems with lazytime enabled. Thanks for that :-)

But remounting with mount version 2.26.2 sucks. As promised, lazytime can be
enabled. But disabling it or trying to switch between atime, relatime, and
noatime doesn't work.

Starting from

# grep sda /proc/mounts
/dev/sda2 /home ext4 rw,lazytime,noatime,nobarrier,errors=remount-ro 0 0

some strace output:

# strace -o /tmp/st mount -o remount,nolazytime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x2152780, MS_MGC_VAL|MS_REMOUNT|MS_NOATIME,
"nobarrier,errors=remount-ro") = 0

# strace -o /tmp/st mount -o remount,relatime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x1543780, MS_REMOUNT|MS_RELATIME|MS_NOATIME,
"nobarrier,errors=remount-ro") = 0

# strace -o /tmp/st mount -o remount,atime /home
# grep ^mount /tmp/st
mount("/dev/sda2", "/home", 0x1534780, MS_MGC_VAL|MS_REMOUNT,
"nobarrier,errors=remount-ro") = 0

The contents of /proc/mounts isn't changed by all this :-(

Or should I contact the util-linux developers?

-- 
Regards,
Jörg.


  reply	other threads:[~2015-07-11 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 21:53 [GIT PULL] ext4 bug fixes for 4.2-rc2 Theodore Ts'o
2015-07-11 12:07 ` Jörg-Volker Peetz [this message]
2015-07-11 12:07   ` Jörg-Volker Peetz
2015-07-11 21:06   ` Theodore Ts'o
2015-07-12  8:20     ` Jörg-Volker Peetz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55A106EE.3050204@web.de \
    --to=jvpeetz@web.de \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.