All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc_lvm@merlins.org>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Can't mke2fs lv
Date: Mon Feb 11 11:34:01 2002	[thread overview]
Message-ID: <20020211173404.GB23@merlins.org> (raw)

I've never had this problem before, it's on a 2.4.14 kernel with lvm
1.0.1rc4:

gargamel:~# lvscan 
lvscan -- ACTIVE            "/dev/BootMylexLVM/usr" [1.50 GB]
lvscan -- ACTIVE            "/dev/BootMylexLVM/var" [2.00 GB]
lvscan -- ACTIVE            "/dev/BootMylexLVM/home" [115.00 GB]
lvscan -- 3 logical volumes with 118.50 GB total in 1 volume group
lvscan -- 3 active logical volume

I was able to mke2fs /dev/BootMylexLVM/usr just fine.
However, doing var and home fails like this:

gargamel:~# mke2fs  /dev/BootMylexLVM/var 
mke2fs 1.25 (20-Sep-2001)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
262144 inodes, 524288 blocks
26214 blocks (5.00%) reserved for the super user
First data block=0
16 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912

mke2fs: Attempt to write block from filesystem resulted in short write zeroing block 524280 at end of filesystem
gargamel:~# mke2fs  /dev/BootMylexLVM/home
mke2fs 1.25 (20-Sep-2001)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
15073280 inodes, 30146560 blocks
1507328 blocks (5.00%) reserved for the super user
First data block=0
920 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000, 23887872

File size limit exceeded


Did I do something stupid, or do I need to upgrade?
(I did do a quick search on this kind of failure, but didn't find anything)


Details on the VG:
gargamel:~# vgdisplay  -v
--- Volume group ---
VG Name               BootMylexLVM
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                255
Cur LV                3
Open LV               0
MAX LV Size           1023.97 GB
Max PV                255
Cur PV                1
Act PV                1
VG Size               135.94 GB
PE Size               16.00 MB
Total PE              8700
Alloc PE / Size       7584 / 118.50 GB
Free  PE / Size       1116 / 17.44 GB
VG UUID               opNV4o-2l8K-Vdtg-aUBK-c2uT-FbA7-BZFvJx

--- Logical volume ---
LV Name                /dev/BootMylexLVM/usr
VG Name                BootMylexLVM
LV Write Access        read/write
LV Status              available
LV #                   1
# open                 0
LV Size                1.50 GB
Current LE             96
Allocated LE           96
Allocation             next free
Read ahead sectors     120
Block device           58:0

--- Logical volume ---
LV Name                /dev/BootMylexLVM/var
VG Name                BootMylexLVM
LV Write Access        read/write
LV Status              available
LV #                   2
# open                 0
LV Size                2.00 GB
Current LE             128
Allocated LE           128
Allocation             next free
Read ahead sectors     120
Block device           58:1

--- Logical volume ---
LV Name                /dev/BootMylexLVM/home
VG Name                BootMylexLVM
LV Write Access        read/write
LV Status              available
LV #                   3
# open                 0
LV Size                115.00 GB
Current LE             7360
Allocated LE           7360
Allocation             next free
Read ahead sectors     120
Block device           58:2


--- Physical volumes ---
PV Name (#)           /dev/rd/disc0/part5 (1)
PV Status             available / allocatable
Total PE / Free PE    8700 / 1116


Thanks,
Marc
-- 
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
  
Home page: http://marc.merlins.org/   |   Finger marc_f@merlins.org for PGP key

             reply	other threads:[~2002-02-11 11:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 11:34 Marc MERLIN [this message]
2002-02-11 12:11 ` [linux-lvm] Can't mke2fs lv Heinz J . Mauelshagen
2002-02-11 12:30   ` Marc MERLIN
2002-02-11 14:08     ` Andreas Dilger
2002-02-11 14:25       ` Marc MERLIN

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=20020211173404.GB23@merlins.org \
    --to=marc_lvm@merlins.org \
    --cc=linux-lvm@sistina.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.