public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean Hunter" <sean@uncarved.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops every write with ext3 + sync + data=journal
Date: Sat, 5 Apr 2003 13:18:56 +0000	[thread overview]
Message-ID: <20030405131856.GA5107@uncarved.com> (raw)
In-Reply-To: <200304050525_MC3-1-331B-F7E4@compuserve.com>

On Sat, Apr 05, 2003 at 05:24:40AM -0500, Chuck Ebbert wrote:
> Sean Hunter <sean@uncarved.com> wrote:
> 
> 
> >rw,sync,data=journal,nosuid,nodev
> 
> 
> Is there any good reason for using sync and data=journal together?

As I understood it (perhaps incorrectly) if you were mounting a drivE
"sync" data=journal was the way to go.

Perhaps that's wrong.

Sean

  reply	other threads:[~2003-04-05 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-05 10:24 Oops every write with ext3 + sync + data=journal Chuck Ebbert
2003-04-05 13:18 ` Sean Hunter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-05  7:35 Sean Hunter
2003-04-05 11:00 ` Alex Tomas
2003-04-05 21:06   ` Sean Hunter

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=20030405131856.GA5107@uncarved.com \
    --to=sean@uncarved.com \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox