From: Ronny Adsetts <ronny.adsetts@amazinginternet.com>
To: linux-xfs@oss.sgi.com, linux-lvm@sistina.com
Subject: [linux-lvm] Error on unmounting XFS LVM snapshot
Date: Fri Oct 17 15:02:04 2003 [thread overview]
Message-ID: <3F901B15.70609@amazinginternet.com> (raw)
Hi,
Please Cc me on any replies.
I am seeing an error logged when unmounting an LVM snapshot of an XFS
partition. Google doesn't give me much.
I have reproduced this error on a different system using a totally
different disk sub-system (Mylex eXtremeRAID 3000) - the system below
has an Adaptec 2400A.
Details are:
System is XFS on top of LVM on top of hardware RAID.
Software used:
Debian: 3.0 (Mostly)
Kernel: 2.4.21
Kernel patches: Debian standard kernel patches; XFS 1.3.0
LVM utils: 1.0.4-4 (Debian)
XFS utils: 2.5.6-1 (Debian)
Sequence of actions:
1: xfs_freeze -f /home
2: lvcreate -L 1G -s -n home_lv_bak /dev/vg0/home_lv
3: xfs_freeze -u /home
4: mount -t xfs -onouuid,ro,usrquota /dev/vg0/home_lv_bak /mnt/home
5: umount /mnt/home
6: lvremove -f /dev/vg0/home_lv_bak
On step 5 of above, an error is logged:
Logs:
Oct 17 17:23:44 jettero kernel: lvm - lvm_map: ll_rw_blk write for
readonly LV /dev/vg0/home_lv_bak
Oct 17 17:23:44 jettero kernel: xfs_force_shutdown(lvm(58,10),0x1)
called from line 351 of file xfs_rw.c. Return address = 0xc01fd6aa
Oct 17 17:23:44 jettero kernel: Filesystem "lvm(58,10)": I/O Error
Detected. Shutting down filesystem: lvm(58,10)
Oct 17 17:23:44 jettero kernel: Please umount the filesystem, and
rectify the problem(s)
There is no oops and machine seems stable enough, though it's only been
running a couple of days since I first did this.
Is this anything to worry about? Is this a known problem? Are there any
patches to fix it?
Thanks and regards,
Ronny Adsetts
--
Technical Director
Amazing Internet Ltd, London
t: +44 20 8607 9535
f: +44 20 8607 9536
w: www.amazinginternet.com
reply other threads:[~2003-10-17 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F901B15.70609@amazinginternet.com \
--to=ronny.adsetts@amazinginternet.com \
--cc=linux-lvm@sistina.com \
--cc=linux-xfs@oss.sgi.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