search for: autodetection

Hi All, I'm currently trying to install centos 5.4 x86-64bit on a raid 1, so if one the 2 disks fails the server will still be available. i installed grub on /dev/sda using the advanced grub configuration option during the install. after the install is done i boot in linux rescue mode , chroot the filesystem and copy grub to both drives using: grub>root (hd0,0) grub>setup (hd0)

Hello all, I have 2 x 250GB sata disks (sda and sdb). # fdisk -l /dev/sda Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 14939 119997486 fd Linux raid autodetect /dev/sda2 14940 29878

...to set backingfile without setting backingformat. The meaning of this is to let qemu autodetect the backing format when opening the overlay disk. However libvirt >= 6.0 refuses to even pass such disks to qemu (see https://bugzilla.redhat.com/show_bug.cgi?id=1798148). For this reason, move the autodetection earlier and make it explicit. We now autodetect the format of the backing disk at the time of creation of the overlay, and set that as the backing format in the overlay disk itself, allowing libvirt to open the disk later. --- lib/create.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff...

Hi all, experimenting with vol-create-as, I think it should autodetect some data - filesize and backing file format, specifically. However, the current implementation require us to specify both filesize and backing file format. Considering that qemu-img already autodetects these data, there are any reason for the lack of autodetect by libvirt? Should I open a bugzilla issue? Below you can

...is > > to let qemu autodetect the backing format when opening the overlay > > disk. > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > https://bugzilla.redhat.com/show_bug.cgi?id=1798148). > > > > For this reason, move the autodetection earlier and make it explicit. > > We now autodetect the format of the backing disk at the time of > > creation of the overlay, and set that as the backing format in the > > overlay disk itself, allowing libvirt to open the disk later. > > --- > > lib/create.c | 13 +++...

We're getting the below errors about once a day on a system we're trying to set up with RedHat 7.3. This has happened to multiple filesystems on multiple physical and logical disks (basically we've got 4 drives as 2 sets of RAID 1 arrays, details below). Until a week ago, this box was a high-volume IMAP server running RedHat 6.2 with uptimes in the 200-day range, so I don't

IMAP logins via fetchmail are failing on my mailserver root at grelber:/home/esr# tail -f /var/log/mail.err Nov 24 16:56:48 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/cathy Nov 24 16:56:48 grelber dovecot: IMAP(cathy): Fatal: Namespace initialization failed Nov 24 16:57:39 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/cathy...

...all is true, we can select arts immediately instead of wasting time testing the others which aren't going to work. This new patch also does the same for esd. All in all, this patch gives us better control over what drivers have to get tested, and the order they're tested in, and makes the autodetection a bit faster. Patch libao-0.8.3-autodetection.patch attached. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com -------------- next part -------------- A non-text attachment was scrubbed... Name: libao-0.8.3-autodetection.patch Type...

...detect the backing format when opening the overlay > > > disk. > > > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > > https://bugzilla.redhat.com/show_bug.cgi?id=1798148). > > > > > > For this reason, move the autodetection earlier and make it explicit. > > > We now autodetect the format of the backing disk at the time of > > > creation of the overlay, and set that as the backing format in the > > > overlay disk itself, allowing libvirt to open the disk later. > > > --- > > &g...

...backingformat. The meaning of this is > to let qemu autodetect the backing format when opening the overlay > disk. > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > https://bugzilla.redhat.com/show_bug.cgi?id=1798148). > > For this reason, move the autodetection earlier and make it explicit. > We now autodetect the format of the backing disk at the time of > creation of the overlay, and set that as the backing format in the > overlay disk itself, allowing libvirt to open the disk later. > --- > lib/create.c | 13 +++++++++++++ > 1 file c...

...opening the overlay > > > > disk. > > > > > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1798148). > > > > > > > > For this reason, move the autodetection earlier and make it explicit. > > > > We now autodetect the format of the backing disk at the time of > > > > creation of the overlay, and set that as the backing format in the > > > > overlay disk itself, allowing libvirt to open the disk later. > > > &...

...> > > disk. > > > > > > > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1798148). > > > > > > > > > > For this reason, move the autodetection earlier and make it explicit. > > > > > We now autodetect the format of the backing disk at the time of > > > > > creation of the overlay, and set that as the backing format in the > > > > > overlay disk itself, allowing libvirt to open the disk later. &...

Hello fellow CentOS'ers- I've got a system running CentOS 5.0. The motherboard has two onboard SATA ports with two drives attached. I installed the system on a RAID1 setup. However, I'd like to add a hotspare disk to the array. Since there are no additional SATA ports, I've installed an additional controller. After partitioning, the additional drive was easily and successfully

Hi, I'm currently experimenting with software RAID1 on a spare PC with two 40 GB hard disks. Normally, on a desktop PC with only one hard disk, I have a very simple partitioning scheme like this : /dev/hda1 80 MB /boot ext2 /dev/hda2 1 GB swap /dev/hda3 39 GB / ext3 Here's what I'd like to do. Partition a second hard disk (say, /dev/hdb) with three

Hi all, I have a dovecot v2.2.7 installation, and I would like dovecot to autocreate the Maildir mailbox when those mailboxes don't exist. Following the instructions at http://wiki2.dovecot.org/MailboxSettings have had no effect, the errors below are reported. As soon as I create the Maildir manually with maildirmake fetching mail starts working fine, so all of the messages about the

First let me say I am not a true expert, but I am experienced. If this machine you purchased was some name brand, you must be speaking about hardware raid, true? If this is true, it normally presents you with what looks like a standard drive (/dev/sda) for every 2 drives configured as raid-1. Also, most name brand servers give you a bootable machine day one. If you are using software raid,

...ng to setup a samba4 with openchange which uses postfix+dovecot+openldap on a ubuntu 12.04.2 system. I can send outgoing emails but incoming emails fail. I looked up the logs and I get: Mar 5 11:03:48 testerA dovecot: lda(sammy): Error: user sammy: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/var/mail Mar 5 11:03:48 testerA dovecot: lda(sammy): Fatal: Invalid user settings. Refer to server log for more information. any idea what I am doing wrong? Any hints, pointers would be much appreciated. now the user is a virtual user. The...

https://bugzilla.samba.org/show_bug.cgi?id=6996 Summary: syncing backups - autodetect older variants already existing on receiver Product: rsync Version: 3.1.0 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

...@@ AC_SUBST([GUESTFS_DEFAULT_PATH]) > > AC_DEFINE_UNQUOTED([GUESTFS_DEFAULT_PATH], ["$GUESTFS_DEFAULT_PATH"], > [Define guestfs default path.]) > + > +AC_ARG_ENABLE([appliance-fmt-auto], > + [AS_HELP_STRING([--enable-appliance-fmt-auto], > + [enable autodetection of appliance image format @<:@default=no@:>@])], > + [ENABLE_APPLIANCE_FMT_AUTO="$enableval"], > + [ENABLE_APPLIANCE_FMT_AUTO=no]) > + > +if test "x$ENABLE_APPLIANCE_FMT_AUTO" = "xyes"; then > + AC_DEFINE([APPLIANCE_FMT_AUTO], [1],...