Will Murnane schrieb:
Perhaps ZFS could do some very simplistic de-dup here: it has the
B-tree entry for the file in question when it goes to overwrite a
piece of it, so it could calculate the checksum of the new block and
see if it matches the checksum for the block it is overwriting. This
is a
On Mon, Apr 13, 2009 at 01:02, Nicholas Lee wrote:
>> There's also the ACARD device:
>>
>> acard ANS-9010B $250
>> plus 8GB RAM $86
>> plus 16GB CF $44
>>
>> It's also got a battery but can dump/restore the RAM to a CF card.
>> It's physicall
On Mon, Apr 13, 2009 at 07:03, Robert Milkowski wrote:
> Hello Daniel,
>
> Thursday, April 9, 2009, 3:35:07 PM, you wrote:
>
> DR> Jonathan schrieb:
>>> OpenSolaris Forums wrote:
if you have a snapshot of your files and rsync the same files again,
you need to use "--inplace" rsync option
> "nl" == Nicholas Lee writes:
nl> zfs handles so much of what once would have been done in
nl> hardware and by drivers. While this is good, it is leaving
nl> this huge grey area where it is hard for those of us on the
nl> front line
well that's not what I meant though. The
Hi,
The zfs(1M) man page indicates that a ZFS volume should only be used
under special circumstances as below.
/*volume** */
/A logical volume exported as a raw
or block device. This type of
Hi Ravi,
I think a previous bug prevented the use of volumes in non-global zones
and the man page was not updated. This is a bug in the man page. I will
fix this.
I agree that this text here:
http://docsview.sfbay.sun.com/app/docs/doc/819-5461/ftyxh?a=view
A ZFS volume is a dataset that repres
On Mon, 13 Apr 2009, Robert Milkowski wrote:
That's because without --inplace rsync will copy a file first, then
apply changes to it and if successful will remove the old file. So if
the old file is still in snapshot you will end-up with a new copy of
the file and the old copy being kept in a po
Hi,
The zfs(1M) man page indicates that a ZFS volume should only be used
under special circumstances as below.
/*volume** */
/A logical volume exported as a raw
or block device. This type of
Gary,
Thanks ! I was suspecting bug#6596237.
But, with the current usage that does not seem likely.
In any case can you collect the output of :
/usr/sbin/lockstat -HcwP -n 5 -D 20 -s 40 sleep 5
This would tell us if there are any lock contentions. And if the system is
suffering from 6
On Mon, Apr 13, 2009 at 09:08:09AM +0530, Sanjeev wrote:
>
> How full is the pool ?
Only 50%, but it started with two 500-gig LUNs initially. We added
two more when it got up to 300 gigabytes.
# zpool list
NAMESIZE USED AVAILCAP HEALTH ALTROOT
space 1.99T 1.02T 992G5
Hello Daniel,
Thursday, April 9, 2009, 3:35:07 PM, you wrote:
DR> Jonathan schrieb:
>> OpenSolaris Forums wrote:
>>> if you have a snapshot of your files and rsync the same files again,
>>> you need to use "--inplace" rsync option , otherwise completely new
>>> blocks will be allocated for the ne
11 matches
Mail list logo
