Comments on: Expand JFS Filesystem http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/ Blog of Bob Sun, 20 Dec 2009 09:43:58 +0000 hourly 1 http://wordpress.org/?v=3.0 By: citizen http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/comment-page-1/#comment-3034 citizen Mon, 01 Jun 2009 03:26:46 +0000 http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/#comment-3034 Hey thanks rob, I just got that drive into my raid. PS. This page is like the second entry for resizing jfs file systems in the google. --Citizen Hey thanks rob, I just got that drive into my raid.

PS. This page is like the second entry for resizing jfs file systems in the google.

–Citizen

]]> By: syzygy http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/comment-page-1/#comment-326 syzygy Thu, 22 May 2008 13:08:32 +0000 http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/#comment-326 According to the bugzilla, the bug that I encountered has since been resolved, so next time I want to expand the fileserver (I can put 3 more drives in), I'll give it a go. I did not realize that you could create a filesystem without a partition either. I may have to play with this method on my test box and see how it goes. According to the bugzilla, the bug that I encountered has since been resolved, so next time I want to expand the fileserver (I can put 3 more drives in), I’ll give it a go. I did not realize that you could create a filesystem without a partition either. I may have to play with this method on my test box and see how it goes.

]]> By: Sam Stern http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/comment-page-1/#comment-325 Sam Stern Thu, 22 May 2008 12:43:13 +0000 http://www.syzygytech.com/2008/01/21/expand-jfs-filesystem/#comment-325 Hi, I found your post from a google search and thought I'd share the right way to get this done (assuming your statement about gpartd bug is accurate, since I don't use the tool and am planning a single fs on my array). 1) make a new array with your (free) new disks. don't partition it -- it's what is causing your issue. NB: if using software raid (mdadm) use the "-e 1.2" command in the create option to enable arrays bigger than 2TB. 2) jfs_mkfs $new_disks (yes you can make a file system with a raid array without a partiton) 3) copy old tb array to new tb array. 4) stop old array 5) add old array disks to new array and let it rebuild. 6) mount the jfs volume (yes at this point there is 1tb free) 7) remount the jfs volume with the "resize" option (as you previously discussed). 8) all done ;> if one were starting anew, and assuming you are using only one fs on the array, you would: 1) make a new array. 2) skip the partition step. This is key ;> 3) jfs_mkfs 4) use the array and then add new disks later and continue with step 7 above. to prevent further issues later in your array's life I would suggest redoing the array now if you have current backups. NB when restoring from backup, mount using the "no integrity" option to increase restore speed then remount with the integrity keyword to re-enable the fs log ;> hth Sam S. Hi,

I found your post from a google search and thought I’d share the right way to get this done (assuming your statement about gpartd bug is accurate, since I don’t use the tool and am planning a single fs on my array).

1) make a new array with your (free) new disks. don’t partition it — it’s what is causing your issue. NB: if using software raid (mdadm) use the “-e 1.2″ command in the create option to enable arrays bigger than 2TB.
2) jfs_mkfs $new_disks (yes you can make a file system with a raid array without a partiton)
3) copy old tb array to new tb array.
4) stop old array
5) add old array disks to new array and let it rebuild.
6) mount the jfs volume (yes at this point there is 1tb free)
7) remount the jfs volume with the “resize” option (as you previously discussed).
8) all done ;>

if one were starting anew, and assuming you are using only one fs on the array, you would:

1) make a new array.
2) skip the partition step. This is key ;>
3) jfs_mkfs
4) use the array and then add new disks later and continue with step 7 above.

to prevent further issues later in your array’s life I would suggest redoing the array now if you have current backups. NB when restoring from backup, mount using the “no integrity” option to increase restore speed then remount with the integrity keyword to re-enable the fs log ;>

hth

Sam S.

]]>