sda2 cannot be monitored, while sda1 can: # ls -l /dev/sda2 brw-r----- 1 root disk 8, 2 Feb 19 14:22 /dev/sda2 # ls -l /dev/sda1 brw-r----- 1 root disk 8, 2 Feb 19 14:22 /dev/sda1
I'm using the repository version of monit, which is 5.2. Thank you. Martin Pala wrote: > > Hi, > > LVM shouldn't be problem, please can you provide output of "ls -l > /dev/sda2"? Which monit version do you use? There was problem in monit <= > 4.10.1 when the device was symlink - the support for device symlinks was > added in Monit 5.0 (current version is Monit 5.1.1). > > Optionally you can use mount point instead of device. > > Regards, > Martin > > > On May 3, 2010, at 6:43 PM, zachlac wrote: > >> >> I have monit monitoring /dev/sdb1, /dev/sdb2, and /dev/sda1. However, >> /dev/sda2 is a Linux LVM, and when I try to monitor it I get a "Data >> access >> error". My output for fdisk is as follows: >> ---------------------------------------------------------------------------------------------- >> isk /dev/sda: 200.0 GB, 200049647616 bytes >> 255 heads, 63 sectors/track, 24321 cylinders >> Units = cylinders of 16065 * 512 = 8225280 bytes >> >> Device Boot Start End Blocks Id System >> /dev/sda1 * 1 13 104391 83 Linux >> /dev/sda2 14 24321 195254010 8e Linux LVM >> >> Disk /dev/sdb: 200.0 GB, 200049647616 bytes >> 255 heads, 63 sectors/track, 24321 cylinders >> Units = cylinders of 16065 * 512 = 8225280 bytes >> >> Device Boot Start End Blocks Id System >> /dev/sdb1 * 1 12160 97675168+ 83 Linux >> /dev/sdb2 12161 24321 97683232+ 83 Linux >> -------------------------------------------------------------------------------------------- >> >> My monitrc contains the following important lines: >> --------------------------------------------------------------------------------------------- >> check filesystem boot_sda1 with path /dev/sda1 >> start program = "/bin/mount /data" >> stop program = "/bin/umount /data" >> if failed permission 640 then unmonitor >> if failed uid root then unmonitor >> if failed gid disk then unmonitor >> if space usage > 80% for 5 times within 15 cycles then alert >> if space usage > 99% then stop >> # if inode usage > 30000 then alert >> # if inode usage > 250000 then alert >> if inode usage > 80% then alert >> if inode usage > 99% then stop >> group server >> >> check filesystem datafs_sda2 with path /dev/sda2 >> start program = "/bin/mount /data" >> stop program = "/bin/umount /data" >> if failed permission 640 then unmonitor >> if failed uid root then unmonitor >> if failed gid disk then unmonitor >> if space usage > 80% for 5 times within 15 cycles then alert >> if space usage > 99% then stop >> # if inode usage > 30000 then alert >> # if inode usage > 250000 then alert >> if inode usage > 80% then alert >> if inode usage > 99% then stop >> group server >> --------------------------------------------------------------------------------------------- >> >> Why can't I monitor the LVM? >> >> Thank you. >> -- >> View this message in context: >> http://old.nabble.com/-monit--can%27t-monitor-one-of-my-filesystems-tp28437378p28437378.html >> Sent from the monit-general mailing list archive at Nabble.com. >> >> >> >> -- >> To unsubscribe: >> http://lists.nongnu.org/mailman/listinfo/monit-general > > > > -- > To unsubscribe: > http://lists.nongnu.org/mailman/listinfo/monit-general > > -- View this message in context: http://old.nabble.com/-monit--can%27t-monitor-one-of-my-filesystems-tp28437378p28447734.html Sent from the monit-general mailing list archive at Nabble.com. -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general
