mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Castle <dalgoda@ix.netcom.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: e2fsck, LVM and 4096-char block problems
Date: Fri, 19 Oct 2001 11:59:37 -0700	[thread overview]
Message-ID: <20011019115937.A10588@thune.mrc-home.com> (raw)


Using Linus' 2.4.10, unpatched.  (Perhaps I need to patch the LVM stuff ;-)

I wanted to extend /usr/src from 19G to 20G.

I umounted /usr/src, lvextend -L +1G /dev/vg01/src, fsck -f /usr/src,
resize2fs /dev/vg01/src

resize2fs tells me to run fsck.  Hmmmm... I just did.

I poke around a bit more and notice the following:

Oct 19 11:45:41 thune kernel: ll_rw_block: device 3a:00: only 4096-char
blocks implemented (1024)

Of course, dumpe2fs says:
Block size:               4096

I tried -f on the resize, and got LOTS of the 4096-char messages.

Some perhaps pertinent information.

thune:~# vgdisplay /dev/vg01
--- Volume group ---
VG Name               vg01
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                9
Open LV               8
MAX LV Size           255.99 GB
Max PV                256
Cur PV                5
Act PV                5
VG Size               150.29 GB
PE Size               4 MB
Total PE              38473
Alloc PE / Size       28746 / 112.29 GB
Free  PE / Size       9727 / 38 GB
VG UUID               xdzl14-LsZ2-IA1c-dGk4-F8EK-xPlt-DV31mQ


thune:~# lvdisplay /dev/vg01/src
--- Logical volume ---
LV Name                /dev/vg01/src
VG Name                vg01
LV Write Access        read/write
LV Status              available
LV #                   1
# open                 0
LV Size                19 GB
Current LE             4864
Allocated LE           4864
Allocation             next free
Read ahead sectors     120
Block device           58:0


Obviously I have the option of creating a new volume and moving things over
to that, but that sort of defeats the purpose of these particular tools.

Recommended course of action?

mrc
-- 
     Mike Castle      dalgoda@ix.netcom.com      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

             reply	other threads:[~2001-10-19 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 18:59 Mike Castle [this message]
2001-10-19 19:25 ` Andreas Dilger
2001-10-19 19:35   ` Mike Castle
2001-10-19 19:48     ` Andreas Dilger

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=20011019115937.A10588@thune.mrc-home.com \
    --to=dalgoda@ix.netcom.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®