search for: unwip

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

...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 ign...

...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...

...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 b...

...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...

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: > >

...wing after upgrade to 1.1.2 14678 Office 2003 Pro installer page faults at end of install process 14679 Diablo II Installer from Blizzard account download doesnt work. 14683 Microsoft Money 2007: Crash on program startup 14696 Mordor: the Depths of Dejenol installer crashes when running UNWIP.EXE 14706 Max Payne 2: Windows no longer transparent 14712 offcolour ingame text in Battlefield 1942 14714 intermittant crashes while playing bf1942 14716 distant objects not obscured by fog in bf1942 14720 Steam: uninstaller no longer launches from wine uninstaller 14724 Max Payn...