Hot answers tagged zpool
FreeNAS is a NAS solution, as such, some technical choices are hidden behind whatever firmware, system or GUI such appliance can use. If you get the partition schema used on a given disk inside a ZFS pool made with FreeNAS (small VM example): $ glabel status Name Status Components ...
I think you should reconsider your use of FreeNAS. You've had an uncharacteristically. large. number. of issues. with. your. FreeNAS. installation(s). over. the years. Many of these issues were planning and ZFS design problems. It may be time to refactor or rebuild your environment now that you have some knowledge of best or better-practices.
Don't go down the road of breaking the ZFS array to "rotate" disks offsite. As you've seen, the rebuild time is high and the resilvering process will read/verify the used size of the dataset. If you have the ability, snapshots and sending data to a remote system is a clean, non-intrusive approach. I suppose you could go through the process of having a ...
To get a disk serial requires that it is running and available: camcontrol identify <device> |grep ^serial (this might be (S)ATA specific) smartcl -i <device> |grep ^Serial reading the disk label once removed from the enclosure In your case, I think the 3rd solution is the only available. So, Assuming you just want first identify the disk: ...
Type zpool clear raid2 to clear the errors and initiate a scrub. If the errors persist following that, replace the disk. More details about the hardware would help, so this is generic advice. My recommendation for bunch of consumer disks connected to a PC motherboard are different than what I'd do for enterprise-level gear.
After further experimentation I've found a fair solution, however it comes with a significant trade-off. Disks which have been offline'd but not detached can later be brought back online with only an incremental resilvering operation ("When a device is brought online, any data that has been written to the pool is resynchronized with the newly available ...
Yes, you can use sparse files as VDEVs when creating a ZFS pool. Although there was a bug affecting an early Linux ZFS port that prevented it to work, it was fixed four years ago. You shouldn't expect performance or reliability with file based vdevs though. Quoting the zpool manual page: The use of files as a backing store is strongly discouraged. It is ...
The tool tells you what you need to do: "Determine if the device needs to be replaced". The tools are only so intelligent and need you, as the human administrator, to figure some things. The steps required are specific to your hardware and your set up, so you will need to make some decisions based on your knowledge of the system. Take a look at the output ...
Try using this guide: AAron Toponce - ZFS on Linux. Assuming you are trying to create a zfs pool called MyPool, using /dev/sda as a disk, try: # zpool create MyPool sda
Remove "disk" from your command line. It's the cause of the error you're receiving. zpool create MyPool sda
Your new filesystem is in /zpgd0/iSCSI. To access it, you can cd /zpgd0/iSCSI. If it is not currently mounted, you can use zfs mount zpgd0/iSCSI. Due to the naming of the filesystem, I'm betting that you probably want to create a ZFS zvol to present as block storage for iSCSI. If that's the case, what you're doing is taking you down the wrong path.
Basicly there is no official way to recover other than restore from backup. But there is ZFS feature called rewind, that may be possible to remove transactions from the pool to a point that the pool is functional again. The following text is from ZFS Internals blog part #11 DO NOT TRY IT IN PRODUCTION. USE AT YOUR OWN RISK! zpool import -FX mypool ...
You just need to create the pool with encryption enabled for its top dataset: zpool create -O encryption=on ...
Finally I've found that my ZFS pool is not corrupted. Old server imports/exports pool without any problem. The only difference was in ZFS kernel version and modules versions: Old: kernel 3.13.0-39-generic, SPL: v0.6.3-1~trusty, ZFS: v0.6.3-3~trusty New: kernel 3.13.0-43-generic, SPL: v0.6.3-3~trusty, ZFS: v0.6.3-5~trusty And, zfs slices were made in ...
Yes, you've rendered your disks unusable... Maybe there's some ZDB magic that can help, but creating RAID 0 HP Logical Drives is a pretty deliberate action. There would have been a clear warning that the data contained on the disks would be lost because of the Smart Array metadata. In general, multiple RAID 0 Logical Drives for ZFS is a bad idea behind a ...
ZFS mirrors are usually much better than RAIDZ(1/2/3) for a variety of reasons (performance, expansion, sanity). This confusion about displayed size is one of them. Please see: Why is my RAIDZ2 pool larger than the expected size calculation?
Only top voted, non community-wiki answers of a minimum length are eligible