From: "Mike Kirk" <mike.kirk@sympatico.ca>
To: linux-lvm@redhat.com
Subject: [linux-lvm] 2TB partition size limit in LVM2? Or ReiserFS?
Date: Sun, 23 Oct 2005 16:08:56 -0400 [thread overview]
Message-ID: <003b01c5d80d$98ec13b0$1b00a8c0@cruncher> (raw)
[-- Attachment #1: Type: text/plain, Size: 1994 bytes --]
Hi all,
I've used LVM2 in the past, and have followed the steps in the LVM HOWTO, but have run into problems trying to grow a reiser3 filesystem. The filesystem has worked fine for several months, but now I'm trying to make it larger...
I've added a pv and am showing free PE's:
--- Volume group ---
VG Name vg
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 11
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 2
Act PV 2
VG Size 2.44 TB
PE Size 4.00 MB
Total PE 639113
Alloc PE / Size 320597 / 1.22 TB
Free PE / Size 318516 / 1.22 TB
VG UUID bADYIh-N4mr-LTJS-5h6b-izph-pgpT-exoOTh
....and I can plug those free PE's into lvextend:
lvextend -l+318516 /dev/vg/lv
> Extending logical volume lv to 2.44 TB
> Logical volume lv successfully resized
....but resize_reiserfs gives errors:
resize_reiserfs /dev/vg/lv
> resize_reiserfs 3.6.19 (2003 www.namesys.com)
>
> bread: Cannot read the block (328029183): (Invalid argument).
>
> reiserfs_open: Your partition is not big enough to contain the
> filesystem of (328029183) blocks as was specified in the found super block.
Nothing is written to syslog when resize_reiserfs runs. How can I tell if this is a LVM2 error providing wrong sizes... or if it's reiserfs tools having the problems? If I lvreduce things to the initial size I can remount things OK, and reiserfsck reports no errors.
This is an AMD2700+ system running 2.6.13.4, a ReiserFS3 3.6 filesystem w/ v3.6.19 reiserfsprogs, and LVM2 v2.01.09 utils
Any suggestions are appreciated.
Thanks!
Mike
[-- Attachment #2: Type: text/html, Size: 5464 bytes --]
reply other threads:[~2005-10-23 20:04 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='003b01c5d80d$98ec13b0$1b00a8c0@cruncher' \
--to=mike.kirk@sympatico.ca \
--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 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).