public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Chris Mason <mason@suse.com>
Cc: Alexander Viro <viro@math.psu.edu>,
	Andreas Dilger <adilger@turbolinux.com>,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com,
	lvm-devel@sistina.com,
	"ext3-users@redhat.com" <ext3-users@redhat.com>
Subject: Re: [PATCH] LVM snapshot support for reiserfs and others
Date: Fri, 10 Aug 2001 13:04:27 -0700	[thread overview]
Message-ID: <3B743E4B.DA2573F3@zip.com.au> (raw)
In-Reply-To: <Pine.GSO.4.21.0108091856020.25945-100000@weyl.math.psu.edu> <992230000.997472946@tiny>

Chris Mason wrote:
> 
> 
> Hi guys,
> 
> Here's a new patch against 2.4.8-pre8, updated to Al's new super
> handling.  The differences between the original are small,
> but they are big enough that I want extra testing from the
> LVM guys (and ext3/XFS).

ext3 will probably lock up on unmount with 2.4.8-pre8.  The fix is
to replace fsync_dev with fsync_no_super in fs/ext3/super.c and
fs/jbd/recovery.c.  I'll be generating a new patchset this weekend.

-

  reply	other threads:[~2001-08-10 19:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 18:35 [PATCH] LVM snapshot support for reiserfs and others Chris Mason
2001-08-09 19:22 ` Andreas Dilger
2001-08-09 20:34   ` Chris Mason
2001-08-09 20:58     ` Andreas Dilger
2001-08-09 22:20       ` Chris Mason
2001-08-09 22:24         ` Alexander Viro
2001-08-09 22:42           ` Chris Mason
2001-08-09 23:26             ` Alexander Viro
2001-08-09 23:50               ` Alexander Viro
2001-08-10 19:49               ` Chris Mason
2001-08-10 20:04                 ` Andrew Morton [this message]
2001-08-14 20:25                 ` Andreas Dilger
2001-08-22  4:06                 ` Chris Mason
     [not found] <no.id>
2001-08-10 22:01 ` Alan Cox

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=3B743E4B.DA2573F3@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=adilger@turbolinux.com \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvm-devel@sistina.com \
    --cc=mason@suse.com \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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