kjcsb wrote: > I notice the following in the log file on booting: > > Jun 9 14:49:26 conversant01 kernel: md: Autodetecting RAID arrays. > Jun 9 14:49:27 conversant01 kernel: md: autorun ... > Jun 9 14:49:27 conversant01 kernel: md: ... autorun DONE. > Jun 9 14:49:27 conversant01 kernel: device-mapper: 4.5.0-ioctl > (2005-10-04) initialised: dm-devel@xxxxxxxxxx > Jun 9 14:49:27 conversant01 kernel: EXT3 FS on sdb1, internal journal > Jun 9 14:49:27 conversant01 kernel: kjournald starting. Commit > interval 5 seconds > Jun 9 14:49:27 conversant01 kernel: EXT3 FS on sda1, internal journal > Jun 9 14:49:27 conversant01 kernel: EXT3-fs: mounted filesystem with > ordered data mode. > Jun 9 14:49:27 conversant01 kernel: kjournald starting. Commit > interval 5 seconds > Jun 9 14:49:28 conversant01 kernel: EXT3-fs warning: maximal mount > count reached, running e2fsck is recommended > Jun 9 14:49:28 conversant01 kernel: EXT3 FS on sdc1, internal journal > Jun 9 14:49:28 conversant01 kernel: EXT3-fs: mounted filesystem with > ordered data mode. > Jun 9 14:49:28 conversant01 kernel: Adding 1044216k swap on /dev/sdb2. > Priority:-1 extents:1 across:1044216k > > I guess it's fairly fundamental misconfiguration and I would appreciate > any advice to correct it. > It is not an error, it is a warning that you should run maintenance on the file system. After x mounts, or y time, you should run e2fsck on the file system. Because you do not want to run it on a r/w mounted file system, shutting down using "shutdown -Fr now" is a good way to do it. It will reboot the system, and check all the file systems. On the other hand, you can just ignore the warning. Most of the time, the check will not find any problems. But it is usualy better to find any problems early, while they are small problems, rather then later, after they become big problems. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
