From: Steve Lord <lord@sgi.com>
To: Shawn Starr <spstarr@sh0n.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ANNOUNCEMENT: XFS patches with rmap12e + 2.4.18-pre9
Date: 13 Feb 2002 09:54:03 -0600 [thread overview]
Message-ID: <1013615643.5428.26.camel@jen.americas.sgi.com> (raw)
In-Reply-To: <1013499333.3572.8.camel@coredump>
In-Reply-To: <Pine.LNX.4.40.0202110133010.5068-100000@coredump.sh0n.net> <1013499333.3572.8.camel@coredump>
On Tue, 2002-02-12 at 01:35, Shawn Starr wrote:
> Some of you may experience compile problems with quota with XFS. I'm
> working on a patch to be ready for today.
>
> NOTE: Two people have reported problems with XFS + EXT3/EXT2. People
> report the kernel unable to locate superblocks of EXT2/EXT3 filesystems
> with XFS compiled in. Looking for help on this issue and researching.
>
> I'll be also intregrating 2.4.18-pre9-ac1 as well today.
I run mixed ext3 and xfs systems from the current xfs cvs tree.
We also have 2.4.18-pre9 (not ac1) running internally. As for
the superblock issue, you should check if they are allowing mount
to auto determine the filesystem type or not, this would maybe
point to stale data in the block device interface.
Just a guess.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@sgi.com
next prev parent reply other threads:[~2002-02-13 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C675D14.8000508@ucwphilly.rr.com>
2002-02-11 6:34 ` ANNOUNCEMENT: XFS patches with rmap12e + 2.4.18-pre9 + Shawn Starr
2002-02-12 7:35 ` ANNOUNCEMENT: XFS patches with rmap12e + 2.4.18-pre9 Shawn Starr
2002-02-13 15:54 ` Steve Lord [this message]
[not found] ` <1013499043.3533.1.camel@coredump>
[not found] ` <3C69D772.6070008@ucwphilly.rr.com>
2002-02-13 15:16 ` ANNOUNCEMENT: XFS patches with rmap12d + 2.4.18-pre9 + Shawn Starr
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=1013615643.5428.26.camel@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.net \
/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.