New answers tagged

1

I'm not sure, but maybe your MySQL is using sparse files You can try to do your rsync with --sparse or --inplace as explained here : Rsync and sparse files


0

I think this one-line command could help: for i in $(df -h | grep mapper | cut -d" " -f1); do echo $i; lvdisplay --maps $i | grep "Physical volume"; done The output is similar to this: /dev/mapper/myserver-root Physical volume /dev/sda5 /dev/mapper/SambaShares Physical volume /dev/sdb1 Physical volume /dev/sdo1 Physical volume /dev/sdp ...


0

As the error says, you have a problem with the vg_ice1/lv_home filesystem. Type the root password to get into a prompt and run fsck /dev/mapper/vg_ice1-lv_home. There is good chance that the error you are seeing is not related to you moving the disks around. Or it could be that the dying disk did manage to corrupt the home filesystem before you manage to ...


0

in you fstab file add the _netdev flag to the device so the boot process waits for the phyiscal volume to become ready, and retries the mount. so defaults becomes defaults,_netdev and make sure netfs is running on boot too chkconfig netfs on that should do it I hope


1

Agree with Shodanshok that deadline is probably a good idea. Far from convinced that you should be using XFS here. find /volume/data/customer/ -type f -iname "*.ext" -mmin +60 -delete XFS used to be very bad with deleting files - I'm told that most of the bugs in this area have been resolved but not done any hard benchmarking to confirm this. it ...


1

First, XFS is the right choice for this kind if scenario: with XFS is almost impossible to go out of inodes. To increase your delete performance, try the following: use the deadline I/O scheduler rather the the (default) cfq use logbsize=256k,allocsize=64k as mount options (in addition to nodiratime,noatime) To lower the deletes impact on other system ...


0

Assuming you have space in your root filesystem, I would do: mkdir /opt/home && mv /home/* /opt/home && umount /home && rmdir /home && ln -s /opt/home /home At this point you can destroy your rhel-home volume and recreate it again with the desired (shrinked) size, adding the remaining space to your rhel-root volume, then: ...



Top 50 recent answers are included