It is indeed possible. zfs-fuse probably notice the partition got bigger
so it expanded itself automatically to fill it. Perhaps the extra step
isn't in fact necessary.
Gordan
On 2015-11-09 13:25, ioan stan wrote:
I followed below without resizing/stretching the initial partition1.
After booting into redsleeve and yum update I took out the SD card and
I resized partition1 with fdisk on my laptop. I rebooted on dreamplug
with pre-mount option and tried to stretch it with zpool command. I
couldn’t start zfs-fuse, nor use zpool command.
However, after booting again normally, I could see the expected
partition (enlarged) size. Is it possible that the stretching could
have taken place automatically during the booting?
On Oct 30, 2015, at 7:15 PM, Gordan Bobic <[email protected]>
wrote:
OK, guys, this is what I suspect some of you have been waiting for:
https://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/images/
Assumptions:
1) DreamPlug: use internal uSD card
2) SheevaPlug: use USB attached storage (otherwise change /dev/sda
in /etc/fstab to /dev/mmcblk0)
3) GuruPlug: Not 100% sure, but one of either 1) or 2) will be
appropriate depending on how the
device you want to do appears in /dev/
4) On the staging machine the SD slot appears as /dev/mmcblk0 - double
check this to avoid the risk of clobbering the wrong device!
Process (assuming the target is the DreamPlug:
1) Update your *Plug's u-boot as per the instructions here:
http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
Make sure you note down your MAC addresses before you reflash u-boot,
and re-set them afterwards!
2) Download the image and extract it to a uSD card (/dev/mmcblk0 on
the staging machine)
wget -O -
https://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el7/images/kirkwood.img.xz
| xz -cd > /dev/mmcblk0
3) Re-partition (MBR format, use fdisk) the target device to stretch
the root partition to take up all of the device. Leave partition 4
alone. Drop partition 1 and re-create it with the same starting sector
and the default end sector will be the end of the physical disk/card).
Set the partition type for partition 1 to "bf" (Solaris, the image
is a ZFS root!).
4) Connect to the DreamPlug, reset it, interrupt the boot process, and
set the following:
---snip---
setenv baudrate 115200
setenv bootargs 'console=ttyS0,115200 root=ZFS=kirkwood/ROOT'
setenv bootcmd 'usb start; ${loadImage}; ${loadInitrd} ; bootm
0x6400000 0x7400000'
setenv bootdelay 3
setenv loadImage 'ext2load usb 0:4 0x6400000 uImage'
setenv loadInitrd 'ext2load usb 0:4 0x7400000 uInitrd'
setenv machid 0xa63
setenv stderr serial
setenv stdin serial
setenv stdout serial
saveenv
---snap---
Note:
setenv machid 0xa63
is only required on the DreamPlug, not needed on GuruPlug or
SheevaPlug.
5) Then for a single boot do:
setenv bootargs 'console=ttyS0,115200 root=ZFS=kirkwood/ROOT
rd.break=pre-mount'
boot
Dracut will drop you to a shell before the switchroot occurs. Issue:
zpool set autoexpand=on kirkwood
zpool set autoexpand=off kirkwood
This will stretch the pool to fill the whole partition, as enlarged in
step 2) above.
Press Ctrl-D
6) The boot will continue (it may drop you to a shell again, just
press Ctrl-D again if it does).
Log in as root, password is "redsleeve".
I have tried to make sure the image is reasonably sanitized (e.g. no
pre-generated ssh keys), but please apply your usual level of paranoia
as with any image.
The kernel is rpm-ed up, so subject to yum updatability. :)
Currently the latest 3.10.x LT. This will probably get bumped up
to 3.18.x at some point in the not too distant future.
Enjoy. :)
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users
