dev/sda2 has been mounted 30 times without being checked,disk check forced
I'm using Xubuntu Linux, thank you.
Name:
Anonymous2008-03-13 15:52
I'm sorry, I meant "disk" instead of "dick". lol is there any way to fix it?
Name:
Anonymous2008-03-13 15:59
Why would you want to disable it?
Name:
Anonymous2008-03-13 16:02
>>3
Because it is for people that might mess up their machine when doing a lot of stuff on it. I don't do much, read books and watch movies mostly, so I don't need it that much. Increasing the number of unchecked mounts would also help.
>>19
Actually, that's for every Unix system on earth, including Debian and Xubuntu. What, you thought your operating system was developed from scratch, with its own unique design?
Just open a terminal, type man fstab and read it until you understand it. Don't post here again until you're done with that.
Name:
Anonymous2008-03-13 19:53
>>20
Stop being an asshole, not everyone is as smart as you.
Name:
Anonymous2008-03-13 19:55
>>3,9,11,15-17,20
I am the OP and I have successfully trolled you. Seriously, /prog/, what's wrong with you?
DESCRIPTION
tune2fs allows the system administrator to adjust various tunable filesystem parameters on
Linux ext2/ext3 filesystems.
OPTIONS
-c max-mount-counts
Adjust the number of mounts after which the filesystem will be checked by
e2fsck(8). If max-mount-counts is 0 or -1, the number of times the filesystem is
mounted will be disregarded by e2fsck(8) and the kernel.
Staggering the mount-counts at which filesystems are forcibly checked will avoid
all filesystems being checked at one time when using journaled filesystems.
You should strongly consider the consequences of disabling mount-count-dependent
checking entirely. Bad disk drives, cables, memory, and kernel bugs could all cor‐
rupt a filesystem without marking the filesystem dirty or in error. If you are
using journaling on your filesystem, your filesystem will never be marked dirty, so
it will not normally be checked. A filesystem error detected by the kernel will
still force an fsck on the next reboot, but it may already be too late to prevent
data loss at that point.
See also the -i option for time-dependent checking.