On 22 January, 2013 - Ian Collins sent me these 0,9K bytes:
> Since upgrading to Solaris 11.1, I've started seeing snapshots like
>
> tank/vbox/shares%VMs
>
> appearing with zfs list -t snapshot.
>
> I thought snapshots with a % in their name where private objects created
> during a send/receive
On 01/21/13 17:03, Sašo Kiselkov wrote:
Again, what significant features did they add besides encryption? I'm
not saying they didn't, I'm just not aware of that many.
Just a few examples:
Solaris ZFS already has support for 1MB block size.
Support for SCSI UNMAP - both issuing it and honoring
On 22 January, 2013 - Darren J Moffat sent me these 0,6K bytes:
> On 01/21/13 17:03, Sa?o Kiselkov wrote:
>> Again, what significant features did they add besides encryption? I'm
>> not saying they didn't, I'm just not aware of that many.
>
> Just a few examples:
>
> Solaris ZFS already has suppor
On 01/22/2013 12:30 PM, Darren J Moffat wrote:
> On 01/21/13 17:03, Sašo Kiselkov wrote:
>> Again, what significant features did they add besides encryption? I'm
>> not saying they didn't, I'm just not aware of that many.
>
> Just a few examples:
>
> Solaris ZFS already has support for 1MB block
On 01/22/13 11:57, Tomas Forsman wrote:
On 22 January, 2013 - Darren J Moffat sent me these 0,6K bytes:
On 01/21/13 17:03, Sa?o Kiselkov wrote:
Again, what significant features did they add besides encryption? I'm
not saying they didn't, I'm just not aware of that many.
Just a few examples
Maybe 'shadow migration' ? (eg: zfs create -o shadow=nfs://server/dir
pool/newfs)
Michel
On 01/21/13 17:03, Sašo Kiselkov wrote:
Again, what significant features did they add besides encryption? I'm
not saying they didn't, I'm just not aware of that many.
Just a few examples:
Solaris Z
On 01/22/13 13:20, Michel Jansens wrote:
Maybe 'shadow migration' ? (eg: zfs create -o shadow=nfs://server/dir
pool/newfs)
That isn't really a ZFS feature, since it happens at the VFS layer. The
ZFS support there is really about getting the options passed through and
checking status but t
On 01/22/2013 02:20 PM, Michel Jansens wrote:
>
> Maybe 'shadow migration' ? (eg: zfs create -o shadow=nfs://server/dir
> pool/newfs)
Hm, interesting, so it works as a sort of replication system, except
that the data needs to be read-only and you can start accessing it on
the target before the i
On 01/22/13 13:29, Sašo Kiselkov wrote:
On 01/22/2013 02:20 PM, Michel Jansens wrote:
Maybe 'shadow migration' ? (eg: zfs create -o shadow=nfs://server/dir
pool/newfs)
Hm, interesting, so it works as a sort of replication system, except
that the data needs to be read-only and you can start
On 01/22/13 13:29, Darren J Moffat wrote:
Since I'm replying here are a few others that have been introduced in
Solaris 11 or 11.1.
and another one I can't believe I missed since I was one of the people
that helped design it and I did codereview...
Per file sensitively labels for TX configu
On 01/22/2013 02:39 PM, Darren J Moffat wrote:
>
> On 01/22/13 13:29, Darren J Moffat wrote:
>> Since I'm replying here are a few others that have been introduced in
>> Solaris 11 or 11.1.
>
> and another one I can't believe I missed since I was one of the people
> that helped design it and I did
>On 01/22/2013 02:39 PM, Darren J Moffat wrote:
>>
>> On 01/22/13 13:29, Darren J Moffat wrote:
>>> Since I'm replying here are a few others that have been introduced in
>>> Solaris 11 or 11.1.
>>
>> and another one I can't believe I missed since I was one of the people
>> that helped design it
On Mon, 21 Jan 2013, Jim Klimov wrote:
Yes, maybe there were more "cool new things" per year popping up
with Sun's concentrated engineering talent and financing, but now
it seems that most players - wherever they work now - took a pause
from the marathon, to refine what was done in the decade be
> From: Darren J Moffat [mailto:darr...@opensolaris.org]
>
> Support for SCSI UNMAP - both issuing it and honoring it when it is the
> backing store of an iSCSI target.
When I search for scsi unmap, I come up with all sorts of documentation that
... is ... like reading a medical journal when all
On 01/22/2013 04:32 PM, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) wrote:
>> From: Darren J Moffat [mailto:darr...@opensolaris.org]
>>
>> Support for SCSI UNMAP - both issuing it and honoring it when it is the
>> backing store of an iSCSI target.
>
> When I search for scsi unmap, I c
Edward Ned Harvey (opensolarisisdeadlongliveopensolaris) wrote:
From: Darren J Moffat [mailto:darr...@opensolaris.org]
Support for SCSI UNMAP - both issuing it and honoring it when it is the
backing store of an iSCSI target.
When I search for scsi unmap, I come up with all sorts of docume
On 01/22/13 15:32, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) wrote:
From: Darren J Moffat [mailto:darr...@opensolaris.org]
Support for SCSI UNMAP - both issuing it and honoring it when it is the
backing store of an iSCSI target.
When I search for scsi unmap, I come up with al
>Some vendors call this (and thins like it) "Thin Provisioning", I'd say
>it is more "accurate communication between 'disk' and filesystem" about
>in use blocks.
In some cases, users of disks are charged by bytes in use; when not using
SCSI UNMAP, a set of disks used for a zpool will in the en
On 01/22/2013 05:00 PM, casper@oracle.com wrote:
>> Some vendors call this (and thins like it) "Thin Provisioning", I'd say
>> it is more "accurate communication between 'disk' and filesystem" about
>> in use blocks.
>
> In some cases, users of disks are charged by bytes in use; when not usi
On 01/22/13 16:02, Sašo Kiselkov wrote:
On 01/22/2013 05:00 PM, casper@oracle.com wrote:
Some vendors call this (and thins like it) "Thin Provisioning", I'd say
it is more "accurate communication between 'disk' and filesystem" about
in use blocks.
In some cases, users of disks are charge
On 01/22/2013 05:34 PM, Darren J Moffat wrote:
>
>
> On 01/22/13 16:02, Sašo Kiselkov wrote:
>> On 01/22/2013 05:00 PM, casper@oracle.com wrote:
Some vendors call this (and thins like it) "Thin Provisioning", I'd say
it is more "accurate communication between 'disk' and filesystem"
On 2013-01-22 14:29, Darren J Moffat wrote:
Preallocated ZVOLs - for swap/dump.
Sounds like something I proposed on these lists, too ;)
Does this preallocation only mean filling an otherwise ordinary
ZVOL with zeroes (or some other pattern) - if so, to what effect?
Or is it also supported to d
Darren J Moffat wrote:
It is a mechanism for part of the storage system above the "disk" (eg
ZFS) to inform the "disk" that it is no longer using a given set of blocks.
This is useful when using an SSD - see Saso's excellent response on that.
However it can also be very useful when your "disk"
On 01/22/2013 10:45 PM, Jim Klimov wrote:
> On 2013-01-22 14:29, Darren J Moffat wrote:
>> Preallocated ZVOLs - for swap/dump.
>
> Or is it also supported to disable COW for such datasets, so that
> the preallocated swap/dump zvols might remain contiguous on the
> faster tracks of the drive (i.e.
On 2013-01-22 23:03, Sašo Kiselkov wrote:
On 01/22/2013 10:45 PM, Jim Klimov wrote:
On 2013-01-22 14:29, Darren J Moffat wrote:
Preallocated ZVOLs - for swap/dump.
Or is it also supported to disable COW for such datasets, so that
the preallocated swap/dump zvols might remain contiguous on the
IIRC dump is special.
As for swap... really, you don't want to swap. If you're swapping you
have problems. Any swap space you have is to help you detect those
problems and correct them before apps start getting ENOMEM. There
*are* exceptions to this, such as Varnish. For Varnish and any other
On 2013-01-22 23:32, Nico Williams wrote:
IIRC dump is special.
As for swap... really, you don't want to swap. If you're swapping you
have problems. Any swap space you have is to help you detect those
problems and correct them before apps start getting ENOMEM. There
*are* exceptions to this,
On 01/22/2013 11:22 PM, Jim Klimov wrote:
> On 2013-01-22 23:03, Sašo Kiselkov wrote:
>> On 01/22/2013 10:45 PM, Jim Klimov wrote:
>>> On 2013-01-22 14:29, Darren J Moffat wrote:
Preallocated ZVOLs - for swap/dump.
>>>
>>> Or is it also supported to disable COW for such datasets, so that
>>> t
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Nico Williams
>
> As for swap... really, you don't want to swap. If you're swapping you
> have problems.
For clarification, the above is true in Solaris and derivatives, but it's not
unive
The discussion gets suddenly hot and interesting - albeit quite diverged
from the original topic ;)
First of all, as a disclaimer, when I have earlier proposed such changes
to datasets for swap (and maybe dump) use, I've explicitly proposed that
this be a new dataset type - compared to zvol and f
On Tue, Jan 22, 2013 at 11:54:53PM +, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) wrote:
> > From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> > boun...@opensolaris.org] On Behalf Of Nico Williams
> >
> > As for swap... really, you don't want to swap. If you're sw
31 matches
Mail list logo