From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Upgrade to 0.9.1b8 went ok but....
Date: Thu, 26 Jul 2001 13:43:10 +0100 [thread overview]
Message-ID: <20010726134310.B723@btconnect.com> (raw)
In-Reply-To: <20010726081633.A11299@math.ohio-state.edu>; from alden@math.ohio-state.edu on Thu, Jul 26, 2001 at 08:16:33AM -0400
On Thu, Jul 26, 2001 at 08:16:33AM -0400, Dave Alden wrote:
> Hi,
>
> Are you aware that the XFS folks modified LVM to work with XFS (something
> about a new ioctl or such)? They state that if you install the latest
> patches, you'll back out the XFS-specific changes which can cause you to
> lose your XFS filesystem. For more info, see the thread with a subject
> of "When LVM-0.9.1beta7 will be merged to XFS cvs tree?" from:
>
> http://oss.sgi.com/projects/xfs/mail_archive/0107/threads.html#00127
>
> My understanding is that this applies to any LVM patches (including the beta8
> patches).
No I wasn't aware of this, though Patrick may be since he uses XFS.
from http://oss.sgi.com/projects/xfs/mail_archive/0107/msg00132.html:
> All block devices in a XFS kernel need a special patch to add an ioctl
> to set the logical block size. The original poster probably didn't add
> that ioctl to his new hacked in LVM; which will cause all kinds of
> problems with xfs user tools and also probably file system corruption.
next prev parent reply other threads:[~2001-07-26 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 21:57 [linux-lvm] Upgrade to 0.9.1b8 went ok but Gonyou, Austin
2001-07-26 9:46 ` Joe Thornber
2001-07-26 12:16 ` Dave Alden
2001-07-26 12:43 ` Joe Thornber [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-26 19:28 Gonyou, Austin
2001-07-27 18:33 Dale Stephenson
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=20010726134310.B723@btconnect.com \
--to=thornber@btconnect.com \
--cc=linux-lvm@sistina.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.