From: Ed Tomlinson <tomlins@cam.org>
To: linux-lvm@sistina.com
Cc: Chris Mason <mason@suse.com>
Subject: [linux-lvm] VFS locking patch fails on 2.4.4
Date: Sat, 28 Apr 2001 10:38:53 -0400 [thread overview]
Message-ID: <01042810385300.12469@oscar> (raw)
Hi,
The VFS locking patch fails on 2.4.4
oscar% cat ../LVM/linux-2.4.2-VFS-lock.patch | patch -p1
patching file drivers/md/lvm.c
Hunk #1 succeeded at 207 with fuzz 1 (offset 48 lines).
patching file fs/buffer.c
Hunk #1 succeeded at 331 (offset 17 lines).
patching file fs/super.c
patching file include/linux/fs.h
Hunk #1 FAILED at 1093.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/fs.h.rej
patching file kernel/ksyms.c
Hunk #1 succeeded at 177 (offset 2 lines).
This worked with 2.4.4-pre8. This is not too important (yet) since
reiserfs snapshots also have problems. They do not work with pre8.
I get the same messages as previously reported (using debian sid).
I know the lvm is going thru a major paradyne shift but hope to be
able to snapshot my reiserfs partn again soon.
TIA
Ed Tomlinson <tomlins@cam.org>
next reply other threads:[~2001-04-28 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 14:38 Ed Tomlinson [this message]
2001-04-28 21:00 ` [linux-lvm] Re: VFS locking patch fails on 2.4.4 Chris Mason
2001-04-30 1:53 ` Chris Mason
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=01042810385300.12469@oscar \
--to=tomlins@cam.org \
--cc=linux-lvm@sistina.com \
--cc=mason@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).