search for: msg00050

Almighty Repo Maintainers, I believe the current repository version of Xen for Lenny stable may be afflicted with this bug, which prevents domUs from shutting down/rebooting properly. http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00050.html What say you? Best Regards Nathan Eisenberg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20090730/2d71ef90/attachment.htm>

Hello I can see several postings on this mailing-list that people have problem with mounting ext3 partition with mode data=journal. See URL's: https://www.redhat.com/archives/ext3-users/2004-March/msg00000.html https://www.redhat.com/archives/ext3-users/2004-March/msg00050.html We are going to use ext3 on a Compact Flash disk in true IDE mode. We need this filesystem to be as safe and consistent as possible. We can not tolerate any garbage in the files after a crash or sudden power failures. We have then decided to use ext3 with mode data=journal. Can I rely on thi...

...hard W.M. Jones wrote: >As discussed in the emails today, this is the third version addressing >most points from the v1/v2 review. > >You will need to pair this with the changes in libguestfs-common from >this series: > >https://www.redhat.com/archives/libguestfs/2020-September/msg00050.html > I'm going to look at this, but I do not have a machine to try this on, so I will not be able to do any functional testing (i.e. the review will be very much incomplete). But from my limited testing I can tell you it breaks the build for me with the following errors: Making all in g...

...hard W.M. Jones wrote: >As discussed in the emails today, this is the third version addressing >most points from the v1/v2 review. > >You will need to pair this with the changes in libguestfs-common from >this series: > >https://www.redhat.com/archives/libguestfs/2020-September/msg00050.html > The series looks good, I went through as much as I possibly could and that's why it took me so much time, sorry for that. What I like about it is that it is essentially just a different --type for the cryptsetup command and the rest is just refactors and clean-ups. So I'd say A...

...k bad... trying backup blocks... fsck.ext3: Invalid argument while checking ext3 journal for /dev/hdb3 google seems to think that the closest matching problem to what I am having is the link below (thus my reason for being here): https://listman.redhat.com:443/archives/ext3-users/2002-December/ msg00050.html I have attempted the debugfs solution as presented here, but when I try to open the partition in anything other than catastrophic mode (thus the inability to write and attempt setting the journal to 0) cannot be tried, the error is as follows: root@0[root]# debugfs -w /dev/hdb3 debugfs...

v1 posted here: https://www.redhat.com/archives/libguestfs/2017-December/msg00050.html v2 fixes the tests by rewriting relative paths as ./filename (so that filenames like "file:foo" work).

I''m pleased to announce the availability of Xen 3.1.1 -- a bugfix release in the Xen 3.1 series. Many bugs, large and small, are fixed by this release and we recommend that all users and vendors upgrade. The source repository is available using mercurial from: http://xenbits.xensource.com/xen-3.1-testing.hg Binary packages have not yet been prepared for this release. Thanks to

I''m pleased to announce the availability of Xen 3.1.1 -- a bugfix release in the Xen 3.1 series. Many bugs, large and small, are fixed by this release and we recommend that all users and vendors upgrade. The source repository is available using mercurial from: http://xenbits.xensource.com/xen-3.1-testing.hg Binary packages have not yet been prepared for this release. Thanks to

As discussed in the emails today, this is the third version addressing most points from the v1/v2 review. You will need to pair this with the changes in libguestfs-common from this series: https://www.redhat.com/archives/libguestfs/2020-September/msg00050.html Rich.

On Tue, Apr 07, 2020 at 02:33:20PM +0200, Pino Toscano wrote: > On Tuesday, 7 April 2020 14:18:47 CEST Richard W.M. Jones wrote: > > On Tue, Apr 07, 2020 at 01:25:02PM +0200, Pino Toscano wrote: > > > The important thing is still that that you need to have space for the > > > temporary files somewhere: be it /var/tmp, /mnt/scratch, whatever. > > > Because of

Hi, I have been working on a Python application that uses hivex. Meanwhile I have encountered some Python bindings issues which could be fixed. The next issue I see now is about the value_value function. This is briefly documented as: "return data length, data type and data of a value". For Perl, Python and OCaml, this is not true. A tuple is returned for both without the length

...so for the virt-v2v files in general, running it for any content older than 2/3 days. Even better, with the proposed consolidation of temporary directories [1], tmpreaper can be pointed at those directories only, not touching anything else. [1] https://www.redhat.com/archives/libguestfs/2020-April/msg00050.html -- Pino Toscano

Hi there, Forgive me for repeating a question asked about a year ago: > Hi, > > Just wondered if anyone had got the following to work or if there are any > plans to add this functionality. > > * X.509 certificate support for authentication. As used in the likes of > stunnel, mod_ssl etc for client auth. > > * Directory based (LDAP) key lookup. Either

...> I can see several postings on this mailing-list that people have > problem > with mounting ext3 partition with mode data=journal. > > See URL's: > https://www.redhat.com/archives/ext3-users/2004-March/msg00000.html > https://www.redhat.com/archives/ext3-users/2004-March/msg00050.html > > We are going to use ext3 on a Compact Flash disk in true IDE mode. We > need this filesystem to be as safe and consistent as possible. We can > not tolerate any garbage in the files after a crash or sudden power > failures. We have then decided to use ext3 with mode data=jo...

...nTypeVal saying what the hash contains on Ruby. ... and mention that all other language bindings return a tuple / list / array with just two elements as the length can be found from the value? Kind regards, Peter https://lekensteyn.nl [0]: https://www.redhat.com/archives/libguestfs/2014-August/msg00050.html [1]: https://www.redhat.com/archives/libguestfs/2014-August/msg00053.html [2]: https://github.com/Lekensteyn/hivex/compare/master...develop

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

Help please- I am running 3.3.1 on Centos using a 10GB network. I get reasonable write speeds, although I think they could be faster. But my read speeds are REALLY slow. Executive summary: On gluster client- Writes average about 700-800MB/s Reads average about 70-80MB/s On server- Writes average about 1-1.5GB/s Reads average about 2-3GB/s Any thoughts? Here are some additional details: