Tag Info

Hot answers tagged

3

http://fibrevillage.com/storage/169-zfs-arc-on-linux-how-to-set-and-monitor-on-linux this article is very good starting version ZoL 0.6.2 you can set the c_max at runtime, however the ARC size will not be released automatically. to force the RAM to be released it is needed to export the zpool.


3

Ugly, but this would work. Except when it doesen't;). Be very careful when specifying the partitions and when replacing the disks try it in am VM beforehand, setup the virtual disks like your hardware an dry run it 1 or 2 times. make a scrub before you start and take a look at the S.M.A.R.T info from the disks. You would not try this with an already ...


2

In the 1st case, maybe some files of user1 can't be discovered by find(1) because they're hidden by some fs being mounted on top of them? In the 2nd case, maybe something is mounted somewhere under the zfs1 mountpoint and you include that in the space calculation? Incidentally, zfs get -H -o value mountpoint zpool/zfs1 will print just the mountpoint, so ...


2

I'd stick with mainstream filesystems like XFS (as promoted by Red Hat) and rely on ZFS for advanced filesystem needs. This is mainly due to: Mindshare: ZFS knowledge is held in the Linux, FreeBSD and Solaris/OpenIndiana communities. Maturity: The ZFS codebase is proven and has been around for awhile. Best-practices have evolved and I can't recall seeing ...


2

I've given an elaborate answer already here: Is btrfs production ready? In short: Btrfs is nothing you already want on a production file server. Here are the reasons why: it becomes unpredictable if space is running out, though most core features are considered stable, others aren't yet and it is still a fast moving target. Being a fast moving target means ...


2

After a lot of troubleshooting with some great people over at the OpenZFS GitHub, I can confirm that this is a bug. The real problem is that I created the pool using the last partition of the disk which, on Linux, can be confused as corruption if the partition aligns closely enough with the end of the disk. ZFS creates four labels on the target device for ...


2

As tegbains pointed out in a comment, zfs send streams do not benefit from any storage-level deduplication in place. They also don't benefit from any other settings; this is why zfs send | zfs receive can be used to migrate data to new settings that otherwise would only take effect once the data is rewritten -- such a enabling or disabling deduplication, or ...


2

Do not do this. I repeat: Do not do this! You will get cluster headaches out of this. If metadata changes in meantime, it could cause crashes and/or invalid data returned. These filesystems are not designed to work like this. Do not use them that way. This is especially bad idea with ZFS. If you really have to, use something very very basic, without ...


1

I read on the freebsd forums a post which suggested to use zfs online -e <pool> <vdev> (without needing to offline the vdev first) This ultimately was the solution, but it required that ZFS autoexpand be disabled first: [root@timestandstill ~]# zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT dfbackup 214G 207G ...


1

More RAM might be a good option. If read performance is not critical, but metadata operations are: I would recommend setting "primarycache" to "metadata" for your filesystems. If you have SSDs for L2ARC, you can also choose to use memory (ARC) for caching "all" and secondarycache (L2ARC) as "metadata". Please note that the other way around does not work ...


1

Use one or the other. I suggest using /etc/exports for consistency and readability, especially if your NFS server is serving data from non-ZFS filesystems.


1

I suspect the ATA driver is retrying the read operation a couple of times when it receives an error before passing the error back to the filesystem driver. What this means is by the time the ZFS filesystem driver gets the result of the read the data is all there, and correct, but it likely took a bit longer than normal to happen. There is of course no error ...


1

I believe you are misunderstanding the ZIL purpose. You describe it as a write cache which it is not. No activity on the ZIL might just be a normal behavior depending on what is running on your machine. Nothing is ever anything read from the ZIL, this is a write only device outside possibly at mount time after a crash. There are only writes to it if ...


1

Ok, so this is definitely due to my inexperience with ZFS. Unlike a traditional file system where you can reference a particular partition from any context, ZFS seems to retain the exact information used to reference the data location no matter where it is loaded from. For example, I created the zpool and referenced the device by from OSX by "/dev/disk0s6" ...


1

This sounds terrible. It's your data, so you can do as you wish... Nobody would endorse the solution, though. This is really a situation where you should just start over. Move your data somewhere temporarily and rebuild.


1

Just run a zpool clear solaris then post the result of zpool status -v. It would be nice to know the hardware involved and what controller you're using. edit Looking at your blkid output, you have remnants of a previous Linux software RAID. You'll need to mdadm --zero-superblock /dev/sdb1 to clear that.


1

It's always better to use redundant pools instead of non-redundant pools (though not always possible). The issue above is not likely to happen on a redundant pool. And it's faster to clone a snapshot (to get a file from it) than to recreate it somewhere (if you, of course, have no complaints about faulty hardware).


1

patched within ZFS on Linux: https://github.com/zfsonlinux/zfs/pull/3404 get the git version and compile it: git clone https://github.com/zfsonlinux/zfs.git



Only top voted, non community-wiki answers of a minimum length are eligible