Den 08. okt. 2016 21:27, skrev Kai Krakow: > > You may want to try setting your io scheduler to deadline (or even noop > if you are using a RAID controller with bbu and write cache). Since you > seem to prefer response times over throughput you should be using > deadline io scheduler anyways. Actually, don't use the default CFQ if > your server is virtualized. At least in my tests, CFQ seems to work a > lot against what virtualized IO seems to achieve. > > I also suggest using maybe XFS as a filesystem. Which one are you using? > I second XFS and deadline, at least on RAID or on a VM. I got bitten by XFS recently though, had a crash with the linux-4.8.0 bug which left my root fs in a bad state. I had no xfs_repair in my initramfs, (no help from genkernel) and the systemrescueCD images from portage were stored on the non-mountable fs :-). My GRML CD had a version of xfs_repair that was too old to deal. Had to find a lap-top and plug it straight to the outside line and get a systemrescueCD from some shady download-provider. Believe it was sourceforge. Make sure you have an up-to date systemrescueCD with recent-ish xfsprogs residing in you boot device if you go XFS for your root-device. fsck.xfs is basically a no-op, so if bad things happen, you mount to play back the journal, then umount, then xfs_repair.
Packages: app-admin/systemrescuecd-x86 (doctored to store latest .iso on your boot-device, which you back up to memory-stick) sys-boot/systemrescuecd-x86-grub sys-fs/xfsprogs (up to date !)
