From: Chung Hsien Hu <mozo@coventive.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] snapshot problem when memory size is over 4GB
Date: Thu, 03 Mar 2005 17:50:51 +0800 [thread overview]
Message-ID: <4226DDFB.8000801@coventive.com> (raw)
In-Reply-To: <e5146c2a050302230579216b77@mail.gmail.com>
Hi,
I got a server with Tyan5350 mainboard and 8GB ECC RAM. And
it seem that snapshot didn't work in either LVM1 or LVM2 when
the memory over 4GB is plugged. We have HIGHMEM64G=y kernel
option been set. Everything is ok when the comination is
"snapshot + 4GB RAM" or "no snapshot + 8GB RAM"...
Any clues?
PS: Hope you could understand my question, english is not my
mother language. :(
1. in linux-2.4.27 + LVM-1.0.8, it failed to activate the VG with
any existed snapshot volume.
bash-2.03# vgchange -ay
vgchange -- ERROR "Bad address" activating volume group "storage"
2. And again, in linux-2.4.27 + LVM-1.0.8, it failed to create snapshot
volume.
bash-2.03# lvcreate -A n -s -n test_snap -l 16 /dev/storage/test
lvcreate -- WARNING: the snapshot will be automatically disabled once it
gets full
lvcreate -- INFO: using default snapshot chunk size of 64 KB for
"/dev/storage/test_snap"
lvcreate -- ERROR "Cannot allocate memory" creating VGDA for
"/dev/storage/test_snap" in kernel
3. Then I turn to test linux-2.6.10 + LVM2. This time I can create a
snapshot and it work well until
I reboot the system. The system will crash when I try to make a tarfile
over the original volume.
bash-2.03# lvm version
LVM version: 2.00.31 (2004-12-12)
Library version: 1.00.19-ioctl (2004-07-03)
Driver version: 4.3.0
bash-2.03# lvm lvscan
ACTIVE Original '/dev/storage/test' [1.95 GB] inherit
ACTIVE '/dev/storage/xfs' [1.95 GB] inherit
ACTIVE Snapshot '/dev/storage/test_snap' [500.00 MB] inherit
ACTIVE '/dev/storage/sysvolume' [2.44 GB] inherit
bash-2.03# tar cvf /mnt/xfs/test.tar /mnt/test
a /mnt/test/ directory
a /mnt/test/ACARD101RC3.iso 67534848 bytes, 131904 tape blocks
===>SYSTEM CRASHED!!......
system halt and the last line of messages on screen is:
<0>Kernel panic - not syncing: Fatal execption in interrupt
It's interesting to mention that the snapshot work well before reboot. Seem
it is kind of problem relate to VFS cache, snapshot and HIGHMEM support?
--
Mozo Hu. mozo@coventive
R&D Assistant Manager, Coventive Advance Technologies
next prev parent reply other threads:[~2005-03-03 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 7:05 [linux-lvm] Can't mount logical volume - super block error Sasha Z
2005-03-03 8:05 ` Scott Serr
2005-03-15 16:56 ` Brian McCullough
2005-03-03 9:50 ` Chung Hsien Hu [this message]
2006-05-16 19:10 ` Joe Harvell
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=4226DDFB.8000801@coventive.com \
--to=mozo@coventive.com \
--cc=linux-lvm@redhat.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.