On Mon, 26 Mar 2012, Andrew Gabriel wrote:
I just played and knocked this up (note the stunning lack of comments,
missing optarg processing, etc)...
Give it a list of files to check...
This is a cool program, but programmers were asking (and answering)
this same question 20+ years ago
One of the glories of Solaris is that it is so very observable. Then
there are the many excellent blog posts, wiki entries, and books - some
or which are authored by contributors to this very thread - explaining
how Solaris works. But these virtues are also a snare to some, and it is
not
2012-03-27 11:14, Carsten John write:
I saw a similar effect some time ago on a opensolaris box (build 111b). That
time my final solution was to copy over the read only mounted stuff to a newly
created pool. As it is the second time this failure occures (on different
machines) I'm really
On Tue, Mar 27, 2012 at 3:14 AM, Carsten John cj...@mpi-bremen.de wrote:
Hallo everybody,
I have a Solaris 11 box here (Sun X4270) that crashes with a kernel panic
during the import of a zpool (some 30TB) containing ~500 zfs filesystems
after reboot. This causes a reboot loop, until booted
hi
you did not answer the question, what is the RAM of the server? how many
socket and core etc
what is the block size of zfs?
what is the cache ram of your san array?
what is the block size/strip size of your raid in san array? raid 5 or
what?
what is your test program and how (from what
On Mon, 26 Mar 2012, Mike Gerdts wrote:
If file space usage is less than file directory size then it must contain a
hole. Even for compressed files, I am pretty sure that Solaris reports the
uncompressed space usage.
That's not the case.
You are right. I should have tested this prior to
