similar to: File copy results in 100% CPU load and broken connection

Dear xen-users, in the last two days, two different domUs on two different dom0s had suddenly corrupted filesystems which let to total data loss on both domUs. I have never suffered under this failure before and I guess it is related to XEN. Both domUs were running for long time without any problems and I am pretty sure, that the hard drives are fine (checked with smart checks).

Mapping stable-security to proposed-updates. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Mon, 29 Sep 2014 15:52:19 +0300 Source: xen Binary: xen-docs-4.1 libxen-4.1 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.1 xen-hypervisor-4.1-amd64 xen-system-amd64 xen-hypervisor-4.1-i386 xen-system-i386 Architecture:

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Mon, 29 Sep 2014 15:52:19 +0300 Source: xen Binary: xen-docs-4.1 libxen-4.1 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.1 xen-hypervisor-4.1-amd64 xen-system-amd64 xen-hypervisor-4.1-i386 xen-system-i386 Architecture: source all amd64 Version: 4.1.4-3+deb7u3

Hi All! I have BSD box running 4.6.2-RELEASE ... I build and install samba-3.0alpha20 with key --with-iconv. My smb.conf in global part have next strings: dos charset = CP866 ; unix charset = KOI8-U display charset = CP866 I run utilitys testparm and see the next messages: Conversion from UCS-2LE to CP866 not supported Conversion from UCS-2LE to CP866 not supported

Mapping stable-security to proposed-updates. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 17 Aug 2014 10:39:32 +0300 Source: xen Binary: xen-docs-4.1 libxen-4.1 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.1 xen-hypervisor-4.1-amd64 xen-system-amd64 xen-hypervisor-4.1-i386 xen-system-i386 Architecture:

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 17 Aug 2014 10:39:32 +0300 Source: xen Binary: xen-docs-4.1 libxen-4.1 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.1 xen-hypervisor-4.1-amd64 xen-system-amd64 xen-hypervisor-4.1-i386 xen-system-i386 Architecture: source all amd64 Version: 4.1.4-3+deb7u2

Hi all, See the following for detail: $ rsync -l ftp.cn.debian.org::debian/dists/wheezy/main/installer-amd64/ [snip] drwxr-sr-x 4,096 2015/01/10 18:17:33 . lrwxrwxrwx 18 2015/01/10 18:16:31 current -> 20130613+deb7u2 +b4 drwxr-xr-x 4,096 2013/05/01 05:33:52 20130430 drwxr-sr-x 4,096 2015/01/05 17:25:32 20130613+deb7u2+b4 In the above case, the current

> Hi. > I was trying to make syslinux to display russian letters. > > This page > https://wiki.syslinux.org/wiki/index.php?title=Directives/font says > that for Cyrillic you need a CP855. Is that correct? All other > guides in internet say that you need CP866. The "original" Code Page for Cyrillic for MS-DOS is "cp855". There are several alternative

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just go 1 deeper for your source: rsync -l ftp.cn.debian.org::debian/dists/wheezy/main/installer-amd64/current/ On 04/16/2015 06:21 AM, Hongyi Zhao wrote: > Hi all, > > See the following for detail: > > $ rsync -l > ftp.cn.debian.org::debian/dists/wheezy/main/installer-amd64/ > [snip] drwxr-sr-x 4,096 2015/01/10

Hi. I was trying to make syslinux to display russian letters. This page https://wiki.syslinux.org/wiki/index.php?title=Directives/font says that for Cyrillic you need a CP855. Is that correct? All other guides in internet say that you need CP866. I finally got it working. My config file was encoded in ibm866 correctly, but the problem was the font file itself. I am on Arch Linux, so I run gunzip

Hi, On 26/10/2019 11:53, Ady Ady via Syslinux wrote: > >> Hi. >> I was trying to make syslinux to display russian letters. >> >> This page >> https://wiki.syslinux.org/wiki/index.php?title=Directives/font says >> that for Cyrillic you need a CP855. Is that correct? All other >> guides in internet say that you need CP866. > > > The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi listers :-) Have a problem with mount'n smbfs: - -E koi8-r:cp866 option, error mesg: telefen# mount -t smbfs -o -N,-E=koi8-r:cp866 //samba@tarakan/c /mnt smbfs: Unable to load iconv library: Shared object "libiconv.so" not found : Undefined error: 0 smbfs: can't initialize iconv support (koi8-r:cp866): syserr = No such file

Hello, I am trying to use a W2K share from my laptop. This share is on Fat32 (not sure if it matters). So far I am able either to configure it so it is mountable by non-root user or to configure it so it sees international (russian) characters in filenames on this share. I am on FC3 with the stock Samba (updated to samba-3.0.10-1.fc3). Here is what I did: To make the share user mountable I

xen_4.1.4-3+deb7u3_amd64.changes uploaded successfully to localhost along with the files: xen_4.1.4-3+deb7u3.dsc xen_4.1.4.orig-qemu.tar.gz xen_4.1.4.orig.tar.gz xen_4.1.4-3+deb7u3.debian.tar.gz xen-docs-4.1_4.1.4-3+deb7u3_all.deb xen-utils-common_4.1.4-3+deb7u3_all.deb xen-hypervisor-4.1-amd64_4.1.4-3+deb7u3_amd64.deb xen-system-amd64_4.1.4-3+deb7u3_amd64.deb

xen_4.1.4-3+deb7u2_amd64.changes uploaded successfully to localhost along with the files: xen_4.1.4-3+deb7u2.dsc xen_4.1.4.orig-qemu.tar.gz xen_4.1.4.orig.tar.gz xen_4.1.4-3+deb7u2.debian.tar.gz xen-docs-4.1_4.1.4-3+deb7u2_all.deb xen-utils-common_4.1.4-3+deb7u2_all.deb xen-hypervisor-4.1-amd64_4.1.4-3+deb7u2_amd64.deb xen-system-amd64_4.1.4-3+deb7u2_amd64.deb

Dear all, I''m seeing this strange thing: When I run "*puppet agent -td*" on the node (Nagios, in this example case), puppet fails to install Nagios3 (on Debian) with this: Debug: Executing ''/usr/bin/dpkg-query -W --showformat ${Status} ${Package} > ${Version}\n nagios3'' > Debug: Executing ''/usr/bin/apt-get -q -y -o >

And some more information ... Am 2014-10-13 12:04, schrieb Jonas Meurer: > Am 2014-08-19 12:26, schrieb Jonas Meurer: >> I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU >> with the >> stock kernel. The dom0 runs the same linux kernel and >> xen/4.1.4-3+deb7u1. > > the bug is still reproducible with the latest kernel and Xen packages >

>Submitter-Id: current-users >Originator: Dmitry Sukhodoev >Organization: sputnik >Confidential: no >Synopsis: wrong char encoding in koi8-r table >Severity: serious >Priority: medium >Category: ports >Class: update >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD sputnik.chel.su 4.8-STABLE FreeBSD 4.8-STABLE #0: Mon Jul 7 22:36:36 YEKST 2003

Package: blktap-dkms Version: 2.0.91-1 Severity: normal With both linux-image-3.2.0-4-amd64 and linux-image-3.16-2-amd64 installed, blktap fails to compile for the 3.16-2 kernel, but succeeds for the 3.2.0-4 kernel. (Contrary to the dependency listing below, I do have the headers for 3.16-2 installed.) I am attaching the build log. -- System Information: Debian Release: 7.6 APT prefers

Hey again, Am 2014-08-19 12:26, schrieb Jonas Meurer: > I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU with > the > stock kernel. The dom0 runs the same linux kernel and > xen/4.1.4-3+deb7u1. the bug is still reproducible with the latest kernel and Xen packages from Debian Wheezy. Unfortunately it seems like a corner case, somehow related to the hardware