similar to: Strange (?) device.map in CentOS 7 VM installations

Displaying 20 results from an estimated 1000 matches similar to: "Strange (?) device.map in CentOS 7 VM installations"

2017 Jan 04
0
Strange (?) device.map in CentOS 7 VM installations
On 29/12/2016 11:24 ??, Nikolaos Milas wrote: > ...I have found that all my CentOS 7 installations (VMs under KVM) > have the same /boot/grub2/device.map, which seemingly refers to two > HDs, although the VMs in fact include only one (virtual) HD. > ... > This is NOT the case with my CentOS 5 and CentOS 6 VMs, which all have > a "correct" device map, with a single
2017 Jan 04
3
Strange (?) device.map in CentOS 7 VM installations
On 01/04/2017 03:07 AM, Nikolaos Milas wrote: > Is it normal in CentOS 7 to have a device map with two entries esp. > when the (physical or virtual) hardware has only one hd ? I don't see that on VMs that I manage. Some of the physical machines that I manage do have duplicates in the device.map.
2011 Aug 29
2
Question re: CentOS-6.0, KVM, and /dev/sr0
I am experimenting with KVM and I wish to create a virtual machine image in a logical volume. I can create the new lv without problem but when I go to format its file system then I get these warnings: Warning: WARNING: the kernel failed to re-read the partition table on /dev/sda (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. Warning: Unable to
2017 Jan 05
1
Strange (?) device.map in CentOS 7 VM installations
On Thu, Jan 5, 2017 at 4:04 AM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 4/1/2017 7:37 ??, Gordon Messmer wrote: > > I don't see that on VMs that I manage. Some of the physical machines that >> I manage do have duplicates in the device.map. >> > > Thank you Gordon for your feedback! > > Can others please report the content of /boot/grub2/device.map
2020 May 29
2
Recover from an fsck failure
On Thu, May 28, 2020 19:38, Robert Nichols wrote: > What output do you get from: > > file -s /dev/mapper/vg_voinet01-lv_log > lsblk -f /dev/mapper/vg_voinet01-lv_log > file -s /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log: symbolic link TO '../DM-5' dm-f lsblk -f /dev/mapper/vg_voinet01-lv_log NAME FSTYPE LABEL UUID
2017 Jan 06
2
Strange (?) device.map in CentOS 7 VM installations
On 5/1/2017 11:04 ??, Nikolaos Milas wrote: > Can others please report the content of /boot/grub2/device.map on > their CentOS 7 (physical or virtual) installations? Thank you all for your reports. Since it seems this is generally the case with CentOS 7, does anyone also have access to RHEL 7 installations to verify if this is the case with these installations as well? > And can any
2014 Mar 17
1
Slow RAID resync
OK todays problem. I have a HP N54L Microserver running centos 6.5. In this box I have a 3x2TB disk raid 5 array, which I am in the process of extending to a 4x2TB raid 5 array. I've added the new disk --> mdadm --add /dev/md0 /dev/sdb And grown the array --> mdadm --grow /dev/md0 --raid-devices=4 Now the problem the resync speed is v slow, it refuses to rise above 5MB, in general
2017 May 05
4
CentOS 7 cloned VM cannot boot
On 5/5/2017 8:29 ??, Nikolaos Milas wrote: > I am very puzzled with "unknown filesystem". After more googling, I found this bug report with a very recent fix: https://bugzilla.redhat.com/show_bug.cgi?id=1399487 It seems to me that this may be relevant in our case. If so, may it be that this fix has not been rolled out to CentOS repos yet? What is your opinion and your
2013 Jan 11
4
Define custom ldap libraries when building Dovecot
Hello, I would like to compile Dovecot using custom ldap libraries, located at a particular custom system location. How should I alter the config process to specify that the include dir is "/usr/local/openldap/include" and the lib dir is "/usr/local/openldap/lib64" and not the standard ones (/usr/include/ and /usr/lib64/ respectively) on RHEL/CentOS 5 (x86_64). Note that
2015 Aug 22
4
PROXY protocol
Op 8/21/2015 om 1:31 PM schreef Nikolaos Milas: > On 20/8/2015 11:09 ??, Nikolaos Milas wrote: > >> As soon as I manage to re-build Dovecot with the latest snapshot, >> I'll test it! > > Hello, > > I've built dovecot with a today snapshot from hg > (dovecot-2-2-9f815e781beb) and I am trying to enable haproxy. > > I configured as follows (lines added
2015 Apr 10
0
how can I tell what's on the MBR of /dev/sda?
On 4/9/2015 5:22 PM, Chuck Campbell wrote: > Subject says it. > > I would like to find out if I have anything written on the MBR of a > disk in my system /dev/sda, or any other device. > If there is something there, is it readable, or recognizable to humans? the MBR contains both binary boot code, which is not human readable, and the master partiion table for the device. you can
2017 Jun 01
2
Urgent: Need to change the location of a directory tree
Hi, I am running CentOS 7 (fully updated) on a VM. This has a mounted nfs share (via fstab) (which mounts a remote storage system) on which we have created the home directories of 2 users Here are the home directories: /mynfsmount | |--/user1 |--/user1 We want to move this whole branch from the mounted NFS share to the local disk. What is the way to do so? Would it be enough to create a
2016 Jan 15
2
remote | local blocks in protocol settings
Hello, Where can I find detailed documentation on how "remote" & "local" blocks are used in protocol configuration to provide specific settings for particular IPs/Names? I've been searching around (wiki2, Google) but I found very few things. I also checked in the conf.d directory of the installation and couldn't find anything. One useful thread was here:
2017 May 05
2
CentOS 7 cloned VM cannot boot
On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512
2011 Feb 21
4
Problem with ldap / quotas
Hi, I am trying to enable per user quotas, but I get the following error: Feb 18 23:59:20 vmail dovecot: auth(default): ldap(tester,10.10.100.150): ldap_search((uid=tester)) failed: No such object It seems as if ldapsearch for username/password won't work with my new settings, but I can't find why. I run Dovecot v1.2.11 on CentOS 5.5. I changed my working dovecot.conf (see
2013 May 30
1
Dovecot 2.2 build rpm on Centos6
> -----Original Message----- > From: dovecot-bounces at dovecot.org [mailto:dovecot-bounces at dovecot.org] > On Behalf Of Burak G?RER > Sent: Thursday, May 30, 2013 10:34 AM > To: Nikolaos Milas > Cc: Dovecot Mailing List > Subject: Re: [Dovecot] Dovecot 2.2 build rpm on Centos6 > > On 27-05-2013 16:56, Nikolaos Milas wrote: > > On 27/5/2013 1:07 ??, Birta
2015 Aug 20
2
PROXY protocol
On 20/8/2015 10:35 ??, Tim Groeneveld wrote: > # This is a list of trusted networks... ips are seperated by ", " > # default, empty > haproxy_trusted_networks = 10.1.2.0/24, 10.2.1.0/24 > > # This is the timeout... in seconds. > # default, 3 > # haproxy_timeout = 3 > > # modify your inet listener's to include haproxy=yes > inet_listener { >
2017 Oct 04
2
NFS mount on Centos 7 crashing
On 2/10/2017 11:46 ??, Nikolaos Milas wrote: > Unfortunately, it doesn't work for me. Problem solved - at least in my case - by changing the NFS Export Options (of the NFS shared directory, at the data storage system) from secure to insecure. That is, I changed from: rw,no_root_squash,no_all_squash,secure,nolog to: rw,no_root_squash,no_all_squash,insecure,nolog I don't
2015 Aug 25
2
PROXY protocol
On 22/8/2015 2:56 ??, Nikolaos Milas wrote: > Can we "stamp" log entries originating from different listeners with a > configurable label? Hello, I haven't received any reply on it. Is it possible or not? Thanks, Nick
2013 Apr 09
3
Problem building powerdns from EPEL
Hi, I just tried to build using http://dl.fedoraproject.org/pub/epel/6/SRPMS/pdns-3.1-2.el6.src.rpm on CentOS 6.4 final (kernel: 2.6.32-358.2.1.el6.x86_64), but it failed when looking for ldap libs: Note: I did not change anything in the original spec file. ... + ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu