I anticipated possible problems so before even attempting I had copied
all my data from my 32.4 TiB JFS file-system to my other 76.3 TiB JFS
file-system. Here is what happened when I tried to expand the file-system.
root@dekabutsu: 09:36 AM :/# uname -a
Linux dekabutsu 2.6.39.4-web10g #1 SMP PREEMPT Thu Sep 1 09:07:40 PDT
2011 x86_64 Intel(R) Xeon(R) CPU E5530 @ 2.40GHz GenuineIntel GNU/Linux
sd 0:0:0:3: [sdd] Attached SCSI disk
sd 0:0:0:3: [sdd] 69749987328 512-byte logical blocks: (35.7 TB/32.4 TiB)
sd 0:0:0:3: [sdd] Write Protect is off
sd 0:0:0:3: [sdd] Mode Sense: cb 00 00 08
sd 0:0:0:3: [sdd] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdd: sdd1
sd 0:0:0:3: [sdd] Attached SCSI disk
# echo 1 > /sys/class/scsi_device/0\:0\:0\:3/device/rescan
sd 0:0:0:3: [sdd] 85374958592 512-byte logical blocks: (43.7 TB/39.7 TiB)
sdd: detected capacity change from 35711993511936 to 43711978799104
root@dekabutsu: 09:29 AM :/# parted /dev/sdd
Warning: GNU Parted has detected libreiserfs interface version
mismatch. Found 1-1, required 0. ReiserFS support will be disabled.
GNU Parted 2.2
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: Areca DATA VOLUME (scsi)
Disk /dev/sdd: 43.7TB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 35.7TB 35.7TB jfs
(parted) resize 1 17.4kB 35.7TB
WARNING: you are attempting to use parted to operate on (resize) a file
system.
parted's file system manipulation code is not as robust as what you'll
find in
dedicated, file-system-specific packages like e2fsprogs. We recommend
you use parted only to manipulate partition tables, whenever possible.
Support for performing most operations on most types of file systems
will be removed in an upcoming release.
No Implementation: Support for opening jfs file systems is not
implemented yet.
(parted) rm 1
(parted) mkpart
Partition name? []?
File system type? [ext2]? jfs
Start? 17.4kB
End? 100%
Warning: The resulting partition is not properly aligned for best
performance.
Ignore/Cancel? Ignore
(parted) p
Model: Areca DATA VOLUME (scsi)
Disk /dev/sdd: 43.7TB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 43.7TB 43.7TB jfs
(parted)
root@dekabutsu: 09:31 AM :/# mount -o noatime,nodiratime /dev/sdd1 /data.old
root@dekabutsu: 09:31 AM :/# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 121G 103G 18G 86% /
/dev/root 121G 103G 18G 86% /
rc-svcdir 1.0M 184K 840K 18% /lib/rc/init.d
udev 10M 248K 9.8M 3% /dev
tmpfs 24G 0 24G 0% /dev/shm
/dev/sda1 121G 73G 48G 61% /winxp
/dev/sde1 77T 48T 29T 63% /data2
/dev/sdd1 33T 26T 6.8T 80% /data.old
root@dekabutsu: 09:31 AM :/#
root@dekabutsu: 09:31 AM :/# time mount -o remount,resize /data.old
mount: /dev/sdd1: can't read superblock
real 0m0.350s
user 0m0.000s
sys 0m0.076s
root@dekabutsu: 09:31 AM :/#
dmesg output:
ERROR: (device sdd1): dbExtendFS: function has not returned as expected
ERROR: (device sdd1): remounting filesystem as read-only
ERROR: (device sdd1): jfs_extendfs
root@dekabutsu: 09:31 AM :/# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 121G 103G 18G 86% /
/dev/root 121G 103G 18G 86% /
rc-svcdir 1.0M 184K 840K 18% /lib/rc/init.d
udev 10M 248K 9.8M 3% /dev
tmpfs 24G 0 24G 0% /dev/shm
/dev/sda1 121G 73G 48G 61% /winxp
/dev/sde1 77T 48T 29T 63% /data2
/dev/sdd1 33T 26T 6.8T 80% /data.old
root@dekabutsu: 09:32 AM :/# umount /data.old
root@dekabutsu: 09:32 AM :/#
fsck:
Unfortunately too much output was generated and some was lost. It was
complete normal about 18 minutes into it.
File inode 3633416 has been reconnected to /lost+found/.
File inode 3633414 has been reconnected to /lost+found/.
File inode 3633396 has been reconnected to /lost+found/.
File inode 3633392 has been reconnected to /lost+found/.
File inode 3633362 has been reconnected to /lost+found/.
File inode 3633327 has been reconnected to /lost+found/.
File inode 3633304 has been reconnected to /lost+found/.
File inode 3633286 has been reconnected to /lost+found/.
File inode 3633271 has been reconnected to /lost+found/.
File inode 3633270 has been reconnected to /lost+found/.
File inode 3633269 has been reconnected to /lost+found/.
File inode 3633268 has been reconnected to /lost+found/.
File inode 3633264 has been reconnected to /lost+found/.
File inode 3633255 has been reconnected to /lost+found/.
File inode 3633247 has been reconnected to /lost+found/.
File inode 3633246 has been reconnected to /lost+found/.
File inode 3633240 has been reconnected to /lost+found/.
File inode 3633199 has been reconnected to /lost+found/.
File inode 3633174 has been reconnected to /lost+found/.
File inode 3633171 has been reconnected to /lost+found/.
File inode 3633160 has been reconnected to /lost+found/.
File inode 3633105 has been reconnected to /lost+found/.
File inode 3632835 has been reconnected to /lost+found/.
File inode 3632823 has been reconnected to /lost+found/.
File inode 3632770 has been reconnected to /lost+found/.
File inode 3632570 has been reconnected to /lost+found/.
97099 files reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
Filesystem Summary:
Blocks in use for inodes: 1165784
Inode count: 9326272
File count: 8295150
Directory count: 756781
Block count: 8718748407
Free block count: 1799021911
34874993628 kilobytes total disk space.
2386986 kilobytes in 756781 directories.
27670891171 kilobytes in 8295150 user files.
11924 kilobytes in extended attributes
0 kilobytes in access control lists
10389875 kilobytes reserved for system use.
7196087644 kilobytes are available for use.
Filesystem is clean.
All observed inconsistencies have been repaired.
Filesystem has been marked clean.
**** Filesystem was modified. ****
processing terminated: 5/28/2012 9:53:45 with return code: 0 exit
code: 1.
..|......
real 21m32.142s
user 2m38.885s
sys 2m43.552s
I try running a du on lost+found to see how much data got put in there..
Unfortunately it is just hanging with no access to the disk du uses 100%
cpu with high %sys. I gave more than enough time it should finish even
with 14.8 MB directory size. I have another direcotry that is 9.4
megabytes on another volume and even that one didn't take that long to
run and it hits the disk I/O pretty heavily if not cached.
A ls also hangs. This compared to a ls on a 9.4 megabyte directory:
root@dekabutsu: 10:07 AM :/data2# ls -lsah | grep -i backup
9.4M drwxr-xr-x 2 root root 700K May 25 01:02 backup
root@dekabutsu: 10:07 AM :/data2# cd backup
root@dekabutsu: 10:07 AM :/data2/backup# time du -hs ./
17T ./
real 0m19.269s
user 0m0.044s
sys 0m0.211s
root@dekabutsu: 10:07 AM :/data2/backup# time find | wc -l
89521
real 0m0.641s
user 0m0.064s
sys 0m0.185s
root@dekabutsu: 10:08 AM :/data2/backup#
For shits and gigles I try the resize again:
root@dekabutsu: 10:09 AM :/# mount -o remount,resize /data.old
mount: /dev/sdd1: can't read superblock
root@dekabutsu: 10:09 AM :/#
ERROR: (device sdd1): dbExtendFS: function has not returned as expected
ERROR: (device sdd1): remounting filesystem as read-only
ERROR: (device sdd1): jfs_extendfs
Anyway now copying my data back to the drive on its new file-system.
root@dekabutsu: 12:39 PM :~# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 121G 103G 18G 86% /
/dev/root 121G 103G 18G 86% /
rc-svcdir 1.0M 184K 840K 18% /lib/rc/init.d
udev 10M 228K 9.8M 3% /dev
tmpfs 24G 0 24G 0% /dev/shm
/dev/sda1 121G 73G 48G 61% /winxp
/dev/sde1 77T 48T 29T 63% /data2
/dev/sdd1 40T 937G 39T 3% /data.old
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
