How to Resize a ZFS Pool on FreeBSD

bsddigital-oceanfreebsdzfs

We are using Digital Oceans block storage feature on our FreeBSD system.

When we add a new block storage we get:

da0 at vtscsi0 bus 0 scbus0 target 0 lun 1
da0: <DO Volume 1.5.> Fixed Direct Access SPC-3 SCSI device
da0: 300.000MB/s transfers
da0: Command Queueing enabled
da0: 5120MB (10485760 512 byte sectors)
da0 at vtscsi0 bus 0 scbus0 target 0 lun 1

and it works fine. We created a zpool and a zfs dataset.
On the zpool we set:
zpool set autoexpand=on tank

And then we resize the block storage disc on Digital Ocean.

Here is our problem

geom disk list does not pick up the change UNTIL we export the zpool. And we cannot resize the zpool until system has recognized the new size for the disc.

If we export the zpool it will correctly show the new size with geom disk list. But not until we have done so.

Now we can run zpool online -e tank da0 and the pool and its datasets will have the new size.

We have tried running camcontrol rescan da0but to no avail.

Is there any way to force a rescan to recognize the new disk size? Because now we have to export/unmount all the datasets, and that is not possible on an live envorionment.

Best Answer

camcontrol reprobe da0

will reprobe. after that I only needed: zpool online -e tank da0

Related Solutions

FreeBSD – Fix ZFS Pool Not Automatically Mounted

Sounds like your ZFS isn't enabled in rc.conf...

echo 'zfs_enable="YES"' >> /etc/rc.conf

FreeNAS – How to Fix RAIDZ1 ‘DEGRADED’ and Disk ‘FAULTED’ Issues

I haven't used zfs enough to say on data integrity. zpool list gave raidz1-0 ONLINE 0 0 0 c8t1d0p0 ONLINE 0 0 0 c8t2d0p0 ONLINE 0 0 0 c8t3d0p0 ONLINE 0 0 0

smartctl -d sat,12 -a /dev/rdsk/c8t3d0p0 listed specific attributes. -d sat -d ata -d scsi may get it to work depending on what type of drives you have. look at raw read error rate, relocated sector count, seek error rate, hardware ecc, and pending sector relocation. -t short or -t long instead of -a will start a test. the long test can take one or many hours depending on the drive. the read seak and hardware errors are not neccessarly a failure. how ever if they keep jumping between listings they can be a good indicator. Also some drive manufacturers may require you use their tools to get a drive rma'd.

If I were in your position and unsure about the drive I would get a replacement and after either verifying its good through working with the manufacturer or having it rma. I would put in the extra drive as a hot spare so that if it happens again you have another drive ready and waiting. z2 is not a bad idea either but I would still keep a spare in the wings. with the size of drives now they do take a long time to rebuild and it is possible to hit a 2nd error.

as to corrupted files if you still have an original some where else of one of those "corrupted" files do a md5 calculation of it and then see if the corrupted file's md5 matches. that will tell you if bits got damaged. if not then there may be invisible damage to the files. whether its enough damage to be a problem will be up to you.

Related Topic