Displaying 7 results from an estimated 7 matches for "unwiped".
Did you mean:
unfixed
2007 Feb 20
8
overriding included classes
I believe this has already been discussed[1], but I''d like to add a bit
more to that original discussion and see if anyone has any suggestions.
Here''s what I''m trying to do: we have a set of very thorough "wipe"
scripts that run every night on our workstations. I''d like to stash
these into a class so that I can include them as a group:
class wiped
2018 Mar 12
4
Re: [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.
...e:
> It has to be said it would be really convenient to have a 'zero'
> and/or 'trim' method of some sort.
>
'trim' means discard?
Currently we cannot support discard on block storage since ovirt may need
to wipe
lvs when deleting a disk, and discarding may leave unwiped user data. This
may
change in 4.3 if we switch to wipe on creation instead of wipe after delete.
> qemu-img tries hard to trim the whole disk before using it.
> Unfortunately it does this in different ways across RHEL 7 and
> upstream. With upstream I managed a workaround based on ignor...
2018 Mar 12
0
Re: [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.
...be really convenient to have a 'zero'
>> and/or 'trim' method of some sort.
>>
>
> 'trim' means discard?
>
> Currently we cannot support discard on block storage since ovirt may need
> to wipe
> lvs when deleting a disk, and discarding may leave unwiped user data. This
> may
> change in 4.3 if we switch to wipe on creation instead of wipe after
> delete.
>
>
>> qemu-img tries hard to trim the whole disk before using it.
>> Unfortunately it does this in different ways across RHEL 7 and
>> upstream. With upstream I...
2018 Mar 12
0
Re: [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.
...calling flush after the operation.
It wasn't clear if anything in this process flushes the content to
disk. Is that what transfer.finalize does?
> Currently we cannot support discard on block storage since ovirt may
> need to wipe lvs when deleting a disk, and discarding may leave
> unwiped user data. This may change in 4.3 if we switch to wipe on
> creation instead of wipe after delete.
I think this depends on BLKDISCARDZEROES[1] for the block device? Of
course if you're worried about data remanence for someone who has
access to the physical device then that wouldn't be...
2018 Mar 12
3
Re: [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.
...hat what transfer.finalize does?
>
All PUT requests fsync() before returning. We optimize for complete image
trasfer, not for random io.
> Currently we cannot support discard on block storage since ovirt may
> > need to wipe lvs when deleting a disk, and discarding may leave
> > unwiped user data. This may change in 4.3 if we switch to wipe on
> > creation instead of wipe after delete.
>
> I think this depends on BLKDISCARDZEROES[1] for the block device? Of
> course if you're worried about data remanence for someone who has
> access to the physical device th...
2018 Mar 08
6
Re: [PATCH v4 0/3] v2v: Add -o rhv-upload output mode.
On Thu, Mar 08, 2018 at 12:13:01PM +0000, Nir Soffer wrote:
> On Wed, Mar 7, 2018 at 12:18 AM Richard W.M. Jones <rjones@redhat.com>
> wrote:
>
> > Previous versions:
> > v3: https://www.redhat.com/archives/libguestfs/2018-March/msg00000.html
> > v2:
> > https://www.redhat.com/archives/libguestfs/2018-February/msg00177.html
> > v1:
> >
2008 Aug 22
0
Wine release 1.1.3
The Wine development release 1.1.3 is now available.
What's new in this release (see below for details):
- Beginnings of ddraw overlay support.
- Many more crypt32 functions.
- Improved support for tables in Richedit.
- Support for NETWM window maximization.
- Many installer fixes.
- Tweaks for better PulseAudio support.
- Various bug fixes.
The source is available from the