On Fri, 2006-06-09 at 16:06 +1200, 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. I don't think it is an error. You can tune the mount count setting with tune2fs. Do man tune2fs. It's just a check to make sure the filesystem stays sane. Regards, Patrick -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
