All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Nathan Scott <nathans@sgi.com>
Cc: xfs@oss.sgi.com, jeremy@sgi.com
Subject: Re: review: fix remount vs barrier options
Date: Fri, 21 Jul 2006 16:25:59 +1000	[thread overview]
Message-ID: <44C07377.3060209@sgi.com> (raw)
In-Reply-To: <20060721152807.D1998769@wobbly.melbourne.sgi.com>

Nathan Scott wrote:
> Hi,
> 
> Jeremy has had me scratching my head for a few days trying to
> figure out how the SCSI traces he's looking at can still show
> signs of write barriers being issued to the device, despite a
> "remount,nobarrier" having been done.
> 
> It finally clicked that we are not clearing the buffer flag
> from a previously written log buffer, even though we'll no
> longer set a new flag into a buffer (due to the mount flag
> being cleared), so we _can_ still issue barrier writes when
> remounted without barriers.
> 
> This was made more complicated by the way a freshly mounted
> filesystem with 8 log buffers wouldn't show up the problem,
> since we have to slowly cycle through the "clear" log buffers
> before we see the bug.  This seems like the simplest fix...
> 
> (Hmmm, actually, I wonder if this will also resolve the quota
> log I/O problem that was reported the other day too).
> 
Patch looks good to me.

--Tim

  reply	other threads:[~2006-07-21  6:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21  5:28 review: fix remount vs barrier options Nathan Scott
2006-07-21  6:25 ` Timothy Shimmin [this message]
2006-07-23 19:06 ` Christoph Hellwig
2006-07-24  0:01   ` Nathan Scott
2006-07-24  1:27     ` Nathan Scott
2006-07-25  9:44       ` Christoph Hellwig
2006-07-25 22:21         ` Nathan Scott

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=44C07377.3060209@sgi.com \
    --to=tes@sgi.com \
    --cc=jeremy@sgi.com \
    --cc=nathans@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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.