November 26, 201411 yr Following my issue when expanding my array that in fact had a faulty drive http://lime-technology.com/forum/index.php?topic=36444.0 I swapped my super.dat back to the orignal state and put back the original (working) drive I initially wanted to expand. I then replaced the faulty drive by a precleared drive. Data-rebuilding has just finished and it looks like my files are on the new disk however the reported free space is strange: # df -h |grep md12 /dev/md12 3.7T -923G 4.6T - /mnt/disk12 Web GUI reports 4.99TB available on a a 4TB drive that should be almost full ! Any idea on what would be causing such message? Few more data: fdisk -lu /dev/sdh WARNING: GPT (GUID Partition Table) detected on '/dev/sdh'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdh: 4000.8 GB, 4000787030016 bytes 256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdh1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. root@babylon:~# gdisk /dev/sdh GPT fdisk (gdisk) version 0.8.4 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/sdh: 7814037168 sectors, 3.6 TiB Logical sector size: 512 bytes Disk identifier (GUID): 40428B67-8DC3-437D-80B2-2E56F66C2778 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 7814037134 Partitions will be aligned on 64-sector boundaries Total free space is 30 sectors (15.0 KiB) Number Start (sector) End (sector) Size Code Name 1 64 7814037134 3.6 TiB 8300 mdcmd status | grep -i size diskSize.0=3907018532 rdevSize.0=3907018532 diskSize.1=1465138552 rdevSize.1=1465138552 diskSize.2=1465138552 rdevSize.2=1465138552 diskSize.3=1465138552 rdevSize.3=1465138552 diskSize.4=1465138552 rdevSize.4=1465138552 diskSize.5=1953514552 rdevSize.5=1953514552 diskSize.6=1953514552 rdevSize.6=1953514552 diskSize.7=1953514552 rdevSize.7=1953514552 diskSize.8=1465138552 rdevSize.8=1465138552 diskSize.9=1953514552 rdevSize.9=1953514552 diskSize.10=1465138552 rdevSize.10=1465138552 diskSize.11=1953514552 rdevSize.11=1953514552 diskSize.12=3907018532 rdevSize.12=3907018532 diskSize.13=0 rdevSize.13=0 diskSize.14=0 rdevSize.14=0 diskSize.15=0 rdevSize.15=0 diskSize.16=0 rdevSize.16=0 diskSize.17=0 rdevSize.17=0 diskSize.18=0 rdevSize.18=0 diskSize.19=0 rdevSize.19=0 diskSize.20=0 rdevSize.20=0 diskSize.21=0 rdevSize.21=0 diskSize.22=0 rdevSize.22=0 diskSize.23=0 rdevSize.23=0 Found a similar post here http://lime-technology.com/forum/index.php?topic=30923.0 I got to minor error when running reiserfsck in maintenance mode: root@babylon:~# reiserfsck --check /dev/md12 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md12 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Wed Nov 26 18:08:19 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md12' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Checking Semantic tree: finished 2 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Wed Nov 26 22:14:37 2014 ########### I then ran reiserfsck again with the fix option root@babylon:~# reiserfsck --fix-fixable /dev/md12 reiserfsck 3.6.24 Will check consistency of the filesystem on /dev/md12 and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --fix-fixable started at Wed Nov 26 22:40:10 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md12' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later. Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 1042052 Internal nodes 6534 Directories 79986 Other files 564399 Data block pointers 946146929 (216 of them are zero) Safe links 0 ########### reiserfsck finished at Thu Nov 27 02:26:18 2014 ########### Restarted the array in normal mode and correct size was reported: # df -h |grep md12 /dev/md12 3.7T 3.6T 113G 97% /mnt/disk12
Archived
This topic is now archived and is closed to further replies.