New answers tagged zfs
1
Both the zfs send and the zfs receive are tied to each other when you pipe them together like this. The source system has to crawl the zfs metadata looking for blocks that were written within the incremental interval you are sending. You're then piping that to mbuffer, so that the stream across the ssh session can be somewhat optimized by presenting a ...
0
Oracle recommends that you utilize ASM. If that is not an option, then I would probably choose UFS since you are going to utilize EMC for redundancy and fault tolerance. Choosing ZFS on top of EMC's already provided redundancy seems to over complicate things. ...kiss
0
You have rightly identified the cause - and by the by, even with SCSI UNMAP, it likely would have still occurred, as the support matrix right now for TRIM and UNMAP is abysmal. However, there is a solution nobody has touched on.
First - enable compression (compress=on or compress=lzjb, I'm not a fan of compress=gzip, especially for VM's), none of this will ...
1
ZFS scrub operations operate on some fairly brain-dead principles. Most notably, it only spends time scrubbing when there's nothing else going on. If you poke a pool with just a bit of data access on a fairly constant basis, scrub will effectively starve itself and do nearly nothing.
Tunables to explore, with my quick notes on what it does (I last looked ...
4
Short Answer
No
Long Answer
Quoting from "Chapter 1 Oracle Solaris ZFS File System (Introduction)":
All metadata is allocated dynamically, so no need exists to preallocate inodes or otherwise limit the scalability of the file system when it is first created.
...no limit exists on the number of file systems or the number of files that can be ...
1
Newest controllers usually support metadata from previous controllers of this vendor. If you recover all connection topology on newer controller, i think it could use metadata from disk to construct the raid back.
Common problems could be found, if you have old drivers, wich don`t understand newer controller, but in you case i think it could be fine.
You ...
0
What's your question? I don't see a question mark in your post... :)
If you're asking if this will work... Yes, this will work under any ZFS-compatible OS. If you don't like one, you can move your ZFS data to another OS with ease.
If you're asking if it will perform well... It depends... But really, no, It probably won't. SATA is bad news for what you're ...
0
I use FreeBSD quite a bit, and I am very active in the community... FreeBSD is a Lot like linux, almost anything you could want in in the FreeBSD ports tree... it has bash and zsh for shells... for the most part FreeBSD gives you all the benefits of Gentoo Linux, but it is easier to setup..
As far as ZFS goes FreeBSD 9.1 supports zfs v28 with ...
3
Don't do it. Dedupe on ZFS is bad news if you haven't planned well for it...
What can happen?
Your system can slow down considerably in certain operations. Holding the dedplication table in RAM isn't the best use of resources.
Your system can stall for DAYS if you delete data or filesystems the wrong way.
If there's any doubt, you shouldn't be using ...
0
Specify another location for dumpadm to use crash dumps instead of just disabling them.
dumpadm -d swap
Source: http://comments.gmane.org/gmane.os.solaris.opensolaris.zfs/19529
1
Since you said you've succeeded in mounting the pool using an alternate mountpoint with zpool import -R /mnt poolname your question is really about what's using up the space, not how to change the mountpoint. Instead of using df for space accounting (which only adds up the size of files without any awareness of compression, dedup, snapshots, async destroy, ...
Top 50 recent answers are included
