
Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tlug] Re: Mysterious LVM issue
John, Francois and others.
Thanks for the feedback.
I did indeed do the initial copy as root and then subsequent checks were
done as a plain user, and the second copy attempt as well. So it seems
like the initial 0 reported but everything still fits can be due to the
extra 5% reserved for root.
LV size is reported 218GB of which 5% would be about 10GB, and even if
the 2GB difference between the LV size and the du size is space reserved
for root it would account for why the copy succeeded with 0 bytes left
(even though you would expect root to get different values reported than
other users then, so there is definitely some lying going).
The crazy values after that must be some kind of bug, as Francois noted.
The 232GB reported doesn't add up no matter how you look at it.
If anyone is interested, I attach the tune2fs and lvdisplay logs.
Cheers,
Birkir
birkirb@example.com:~$ sudo /sbin/tune2fs -l /dev/mapper/america_main-store
tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: store
Last mounted on: <not available>
Filesystem UUID: 7684a222-a800-477b-8cd9-b0f3453e4685
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 14344192
Block count: 57361408
Reserved block count: 2868070
Free blocks: 3421556
Free inodes: 14276794
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1010
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Sun Mar 8 18:26:24 2009
Last mount time: Wed Mar 11 18:18:00 2009
Last write time: Wed Mar 11 18:18:00 2009
Mount count: 1
Maximum mount count: 38
Last checked: Wed Mar 11 17:58:26 2009
Check interval: 15552000 (6 months)
Next check after: Mon Sep 7 17:58:26 2009
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 0c4b1477-3920-40dd-b5e0-de2b3ddfa20f
Journal backup: inode blocks
birkirb@example.com:~$ sudo pvdisplay
--- Physical volume ---
PV Name /dev/hda4
VG Name america_main
PV Size 222.54 GB / not usable 2.97 MB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 56970
Free PE 0
Allocated PE 56970
PV UUID waEJHf-j16Y-R1o9-mdAq-c8nS-Z81m-U7Hux8
birkirb@example.com:~$ sudo lvdisplay
--- Logical volume ---
LV Name /dev/america_main/home
VG Name america_main
LV UUID IUzhnE-BJK1-rz35-oS53-4jSi-UJGg-ZFxd8F
LV Write Access read/write
LV Status available
# open 1
LV Size 952.00 MB
Current LE 238
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Name /dev/america_main/local
VG Name america_main
LV UUID 52NL39-FdGo-AIfy-w3IC-3FtC-UhhP-dwPUCU
LV Write Access read/write
LV Status available
# open 1
LV Size 2.79 GB
Current LE 715
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Name /dev/america_main/store
VG Name america_main
LV UUID Dm6jfZ-zg1n-U09h-Vwxd-95nB-459P-46Fx4c
LV Write Access read/write
LV Status available
# open 1
LV Size 218.82 GB
Current LE 56017
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
Home |
Main Index |
Thread Index