case:17437017 NVX 4 x 3TB = only 7408GB. Should be 8100+GB?

[karlblomquist]

I recently expanded drives on one of our NVX systems to 4 3TB drives. Raidar shows each drive being 2794GB in size.

However we are only getting 7408GB total usable space on the system - it seems to me that the space should be closer to 8100+ GB.

Volume.log (below) indicates 'c' is 8.14GB in size, which makes sense to me.

Question is, where is the missing 700GB? We're getting low on space and could use the extra 700GB.

Any help appreciated.

Thanks, Karl


volume.log

===== pvscan =====
PV /dev/md2 VG c lvm2 [5.44 TB / 0 free]
PV /dev/md3 VG c lvm2 [2.73 TB / 0 free]
Total: 2 [2.17 TB] / in use: 2 [2.17 TB] / in no VG: 0 [0 ]
===== vgscan =====
Reading all physical volumes. This may take a while...
Found volume group "c" using metadata type lvm2
===== lvscan =====
ACTIVE '/dev/c/c' [8.17 TB] inherit
===== vgdisplay =====
--- Volume group ---
VG Name c
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 12
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 8.17 TB
PE Size 64.00 MB
Total PE 133920
Alloc PE / Size 133920 / 8.17 TB
Free PE / Size 0 / 0
VG UUID fhovFJ-X066-p19q-E0m8-EIXr-zJjb-LwUhqb

===== lvdisplay /dev/c/c =====
--- Logical volume ---
LV Name /dev/c/c
VG Name c
LV UUID FjXtqG-EFZP-487O-oUi3-hx3B-hhEl-xCoADo
LV Write Access read/write
LV Status available
# open 1
LV Size 8.17 TB
Current LE 133920
Segments 2
Allocation inherit
Read ahead sectors 0
Block device 253:0

===== dumpe2fs /dev/c/c =====
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: /c
Filesystem UUID: 0c810819-5c0f-4456-b2a1-e25a90ac5051
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 121872384
Block count: 1949958144
Reserved block count: 0
Free blocks: 132397465
Free inodes: 121712562
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 559
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 2048
Inode blocks per group: 128
RAID stride: 16
RAID stripe width: 48
Flex block group size: 16
Filesystem created: Fri Jan 7 00:09:19 2011
Last mount time: Wed Dec 21 21:48:18 2011
Last write time: Wed Dec 21 21:48:18 2011
Mount count: 11
Maximum mount count: -1
Last checked: Sun Oct 30 14:32:41 2011
Check interval: 0 (<none>)
Lifetime writes: 3833 GB
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: d336d8c0-f55f-4057-baad-2506b49f9c74
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x000b9dfd
Journal start: 20464

===== fstab =====
#-----------------------------------------------------------------------------
# <device> <mount> <type> <options> <freq> <pass>
#-----------------------------------------------------------------------------
/dev/md0 / ext3 defaults,noatime,nodiratime 0 0
proc /proc proc defaults 0 0
/dev/md1 swap swap defaults 0 0
/dev/c/c /c ext4 defaults,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1,noatime,nodiratime,data=journal 0 2
/XXX /home/ftp/XXX bind bind 0 0


Partition.log

***** partition output for sda *****

Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0D1A7291-8576-42D5-A511-5E05ADF39797
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 8-sector boundaries
Total free space is 4141 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00
2 8388672 9437247 512.0 MiB FD00
5 9437256 3907024064 1.8 TiB FD00
6 3907024072 5860529038 931.5 GiB FD00

Disk /dev/sda: 364801 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8257536 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ - 0- 2147483647+ ee EFI GPT
/dev/sda2 0 - 0 0 0 Empty
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty


fs_check.log

***** File system check performed at Sun Oct 30 14:32:41 EDT 2011 *****
fsck 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/c/c: 158346/121872384 files (3.3% non-contiguous), 1741134049/1949958144 blocks

[mdgm-ntgr]

How many reboots have you done since upgrading to 3TB disks?

What disks did you have in the NAS before?

What version of RAIDiator are you running?

[karlblomquist]

mdgm wrote:
How many reboots have you done since upgrading to 3TB disks? What disks did you have in the NAS before? What version of RAIDiator are you running?

Several reboots - at least 5 - some with days between them.

2TB drives before... added the 3TB drives 1 at a time...

RAIDiator 4.2.18

It's interesting that volume reports 8.14 which is just about what I'd expect, but it's like there's 700GB of "hidden" used space somewhere.

Thanks, Karl

[mdgm-ntgr]

Is this really what partition.log looks like?:

Number Start (sector) End (sector) Size Code Name
1 64 8388671 4.0 GiB FD00 
2 8388672 9437247 512.0 MiB FD00 
5 9437256 3907024064 1.8 TiB FD00 
6 3907024072 5860529038 931.5 GiB FD00

On my ReadyNAS I see Linux RAID in the Name column on these lines.

I would suggest opening a tech support (http://www.readynas.com/support) case. They should be able to look at your logs and work out what's going on.

[karlblomquist]

Hmmm, rereading the volume.log I do notice:
Block count: 1949958144
Block size: 4096
which would total around 74xxGB cap. So is there 700GB in unallocated blocks?

Opened a service req. Attached all logs and a couple of RAIDar pics.

Thanks, Karl

[mdgm-ntgr]

I would suggest you add the case number to the thread title (i.e. edit subject of first post in this thread) in case a NetGear support rep comes across this thread.

[karlblomquist]

A tech support rep recommend an O/S reinstall. Apparently this will NOT affect my data/volume. I'd rather avoid having to do a 7+TB restore if possible, so can anyone confirm that O/S reinstall (besides resetting some config items) will NOT affect the existing volume/data?

Of course I realize nothing is 100%, but in general if O/S reinstall is benign re data then I'll give it a shot. Otherwise I'd just as well wait until we're getting closer to our current (albeit incorrect) limit.

Thanks, Karl

[PapaBear1]

An OS reinstall will reset the password and configuration, but is not supposed to affect data in any way. Of course, as you pointed out Murphy is always lurking. I have never had a problem with an OS reinstall or upgrade, but probably because I keep Murphy at bay with a complete an current backup.