R.G. Keen wrote:
> I didn't see "remove a simple device" anywhere in there.
>
> Is it:
> too hard to even contemplate doing,
> or
> too silly a thing to do to even consider letting that happen
> or
> too stupid a question to even consider
> or
> too easy and straightforward to do the procedure I
Edward Ned Harvey wrote:
>> I use the excellent pbzip2
>>
>> zfs send ... | tee >(md5sum) | pbzip2 | ssh remote ...
>>
>> Utilizes those 8 cores quite well :)
>>
>
> This (pbzip2) sounds promising, and it must be better than what I wrote.
> ;-) But I don't understand the syntax you've got
Bob Friesenhahn wrote:
> On Sun, 6 Dec 2009, Edward Ned Harvey wrote:
>>
>> I also have a "threadzip" script, because gzip is invariably the
>> bottleneck
>> in the data stream. Utilize those extra cores!!! ;-)
>
> Gzip can be a bit slow. Luckily there is 'lzop' which is quite a lot
> more CPU e
Edward Ned Harvey wrote:
>> If feasible, you may want to generate MD5 sums on the streamed output
>> and then use these for verification.
>>
>
> That's actually not a bad idea. It should be kinda obvious, but I hadn't
> thought of it because it's sort-of duplicating existing functionality.
>
Colin Raven wrote:
> On Sat, Dec 5, 2009 at 17:43, Seth Heeren <mailto:s...@zfs-fuse.net>> wrote:
>
> Bob Friesenhahn wrote:
> > On Sat, 5 Dec 2009, Seth Heeren wrote:
> >>>
> >>> in the same way, I guess, when running an OS on a S
Bob Friesenhahn wrote:
> On Sat, 5 Dec 2009, Sriram Narayanan wrote:
>
>> If feasible, you may want to generate MD5 sums on the streamed output
>> and then use these for verification.
>
> You can also stream into a gzip or lzop wrapper in order to obtain the
> benefit of incremental CRCs and some
Bob Friesenhahn wrote:
> On Sat, 5 Dec 2009, Seth Heeren wrote:
>>>
>>> in the same way, I guess, when running an OS on a SSD boot disk,
>>> should we still need the same memory swapping mechanisms as we do
>>> today, considering that in that case, the swap d
Yes. It is my understanding that (at least recent versions) will detect
incomplete transactions and simply rollback to the last consistent
uberblock in case of trouble.
I'm not completely up to speed with regard to the ODF, Uberblocks and
the ZIL; In my recollection the "inspection / selection" of
Selim Daoud wrote:
> I was wondering if there were work done in the area of zfs
> configuration running out of 100% SSD disks.
>
> L2ARC and ZIL have been designed as a way to improve long seek
> times/latencies of rotational disks.
> now if we use only SSD (F5100 or F20) as back end drives for zfs
Well what does _that_ verify?
It will verify that no bits provably broke during transport.
It will still leave the chance of getting an incompatible stream, an
incomplete stream (kill the dump), or plain corrupted data. Of course,
the chance of the latter should be extremely small in server-grade
Andre Boegelsack wrote:
> Hi to all,
>
> I have a short question regarding which filesystem I should use in Dom0/DomU.
> I've built my Dom0 on basis of ZFS.
>
> For my first DomU I've created a ZFS pool and installed the DomU (with OSOL
> inside). During the installation process you are being ask
11 matches
Mail list logo
