search for: appareantly

Hello, I am curious why when using virt-sparsify the apparent-size of the file gets reduced to the actual file size? Is there a way to get the apparent-size left as the full size? In the man page for virt-sparsify it has a section on "IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to indicate what I would expect where "ls -lh" shows the full apparent size

Hello, I am curious why when using virt-sparsify the apparent-size of the file gets reduced to the actual file size? Is there a way to get the apparent-size left as the full size? In the man page for virt-sparsify it has a section on "IMPORTANT NOTE ABOUT SPARSE OUTPUT IMAGES" and its output seems to indicate what I would expect where "ls -lh" shows the full apparent size

Hello Rich, Thanks for the reply and information. > What is file.img? Its simply a file I made while testing sparse files "truncate -s 512M file.img". > 'du --apparent-size' and 'ls -l' are the same thing, so it's not > really surprising that you see the same numbers here. Indeed, I expected those to be the same, just figured I would show them both for

When calculating the initial size of the disk we must estimate how much space is taken by the input. This is quite difficult. For directories we used ‘du --apparent-size -bs DIR’. This is wrong because ’-b’ implies ‘--apparent-size --block-size=1’. But also ‘--apparent-size’ causes du to count the file size rather than number of blocks used by files. If you have a directory containing many

Hello, I've been using NUT and cacti to graph some values from our UPS's. Unfortunately, while the APC UPS's seem to track both apparent (complex) power % and real power %, as best I can tell NUT will only fetch apparent power. ups.load returns apparent power, and I can't find any key that returns real power- we need to know both. Am I missing something? Is there a patch I can

On Wed, Jun 15, 2016 at 10:20:54AM -0500, libvirt_users@skagitattic.com wrote: > Hello, > > I am curious why when using virt-sparsify the apparent-size of the file > gets reduced to the actual file size? Is there a way to get the > apparent-size left as the full size? > > In the man page for virt-sparsify it has a section on > "IMPORTANT NOTE ABOUT SPARSE OUTPUT

On Wed, Jun 15, 2016 at 10:20:54AM -0500, libvirt_users@skagitattic.com wrote: > Hello, > > I am curious why when using virt-sparsify the apparent-size of the file > gets reduced to the actual file size? Is there a way to get the > apparent-size left as the full size? > > In the man page for virt-sparsify it has a section on > "IMPORTANT NOTE ABOUT SPARSE OUTPUT

On Thu, Jun 23, 2016 at 10:57:43AM -0500, libvirt_users@skagitattic.com wrote: > Thanks for all the information, I think my last remaining question is > why the image created with virt-install shows the full apparent size > and the image from virt-sparsify does not? (The image testimage1.qcow2 > created with default options). I don't really know what you mean by "full

вт, 18 лют. 2020 о 10:48 Richard W.M. Jones <rjones@redhat.com> пише: > > When calculating the initial size of the disk we must estimate > how much space is taken by the input. This is quite difficult. > > For directories we used ‘du --apparent-size -bs DIR’. This is wrong > because ’-b’ implies ‘--apparent-size --block-size=1’. But also > ‘--apparent-size’ causes du

Greetings! I am still new to R but have been asked to look at doing astronomy with R. I have a FITS file which contains an optical telescope image (it can be viewed in SAOimageDS9). I need to estimate the magnitude of a galaxy... and eventually other optical sources. How do I find the apparent magnitude of a galaxy from a FITS file? -- View this message in context:

Dear R-devel, Recent versions of R CMD check have been flagging apparent S3 methods that are not registered in the NAMESPACE as such. In most situations this is very helpful. However, I have few cases in existing packages where we have unfortunately named functions using a "." in them that makes them appear as S3 methods when they are not. As there is no existing class

Hello, Thanks for all the information, I think my last remaining question is why the image created with virt-install shows the full apparent size and the image from virt-sparsify does not? (The image testimage1.qcow2 created with default options). As they are both qcow2 I would expect them both to have the same behavior as far as apparent size goes. Or is there an option I am missing in

On Wed, Jun 22, 2016 at 05:56:09PM -0500, libvirt_users@skagitattic.com wrote: > > Delete what you've done and start from the beginning. Describe > > exactly how you created the guest. Use 'qemu-img info' to show the > > format of the input file. Show precisely the virt-sparsify command > > you are running. And use 'qemu-img info' on the output file

Looking around on the Web, what I just tried was to stop the RAID, then do an --assemble --scan, and *that* found everything, put the raid together, and appears to be rebuilding using the new drive. *phew* I do find it interesting that scan works, but explicitly assembling apparently remembers the drive that died, and wouldn't even look at it. mark

Dear list members (especially Xen network wizards), I''m using the netfilter_queue mechanism to modify packets on the wire that are sent from one domU to another while they travel over the dom0 bridge. This has worked fine as long as I was tinkering with UDP packets only - but when I try to reinject TCP frames with an increased length, I run into a BUG() because

Hi, Again I'm doing logistic regression using lrm from Harrell's Design package, but on wide matrices (28 observations, 1891 variables) so L2 penalisation is used. I get the following error, although I've tried different penalties and different tolerances. The X matrix is scaled and centred. > library(Design) >

Hi all, the monorepo contains a Go frontend called 'llgo' (in the llgo/ top level folder). It apparently hasn't been active since 2017 and before that it wasn't very active either (there were 13 commits in 2016 apparently, most of it minor fixes). I would propose that we remove it from the monorepo for the following reasons: * It is apparently unmaintained. * It only supports a

Okay, apparently coff2yaml and yaml2coff are not in a great place as they both don't deal well with the fact that you can have overlapping sections, which seems to be what clang-cl produces (the .data section points to the same place as a later section). Which is not a big big problem for me particularly because msvc doesn't even generate .data sections in .obj. I'm trying to put

yeah, apparently .bss has a flag of unitialized data that is not being respected on the layout of the coff files (it should skip those sections) but I dunno what to do with .data as it doesn't have a size. (resending as apparently my pastes generated a ton of hidden html data and this message hit the mailinglist limit of 100k) -- Leonardo Santagada -------------- next part -------------- An

I have come across an apparent bug in the operation of Sweave. If I load the package R2HTML then execution of \Sexpr{} in an *.Rnw file no longer works. The \Sexpr{} code is simply written to the *.tex file. Below are my *.Rnw file, commands, and output. The Sweave file, Sweave-test-1_short.Rnw: % -*- mode: noweb; noweb-default-code-mode: R-mode; -*- \documentclass{article} \title{A Test