SliTaz Forum

Escapetiger

Member

Registered: 2012-07-24

Posts: 44

Checking filesystems under SliTaz 5

Hello,

On a single hard disk, i've got classical three partitions :

/dev/sda1 / Linux (ext3) boot

/dev/sda2 Linux swap

/dev/sda3 /home Linux (ext3)

By default, every 25 reboot's, the /dev/sda1 is checked. I read (don't remember where at this time) that Slitaz do not have "maintenance" mode (typically differents runlevel).

How to check the /dev/sda3 (/home) partition ? and is there a need to do that without warning messages?

...

I try e2fsck (options -n no changes and -f forced) command as below, don't know if the informations in this case are to be considered as relevant :

/sbin/e2fsck -n  /dev/sda3

e2fsck 1.42.5 (29-Jul-2012)

Warning!  /dev/sda3 is mounted.

Warning: skipping journal recovery because doing a read-only filesystem check.

/dev/sda3: clean, 1114/2281104 files, 1337155/9111808 blocks

/sbin/e2fsck -n -f  /dev/sda3

e2fsck 1.42.5 (29-Jul-2012)

Warning!  /dev/sda3 is mounted.

Warning: skipping journal recovery because doing a read-only filesystem check.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Entry 'sessionstore.json' in /tux/.mozilla/seamonkey/ibfc0n0j.default (686847) has deleted/unused inode 687174.  Clear? no

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Unattached zero-length inode 687169.  Clear? no

Unattached inode 687169

Connect to /lost+found? no

Pass 5: Checking group summary information

Block bitmap differences:  +2766848 -2766849 +(2766850--2766851) -(2766852--2766853)

Fix? no

Free blocks count wrong (7774653, counted=7774186).

Fix? no

Inode bitmap differences:  +687169 -687174

Fix? no

Free inodes count wrong (2279990, counted=2279951).

Fix? no

/dev/sda3: ********** WARNING: Filesystem still has errors **********

/dev/sda3: 1114/2281104 files (15.4% non-contiguous), 1337155/9111808 blocks

yves04

Member

Registered: 2012-09-23

Posts: 135

Re: Checking filesystems under SliTaz 5

Hi

Never check any partition if it is mounted. You have to boot from the live CD or USB live and then open xterm or sakura,login as root and type

e2fsck /dev/sda3

For 30 days before the next checking, use the command

tune2fs -c 30 /dev/sda3

Have a nice day

devl547

Administrator

Registered: 2011-06-01

Posts: 285

Re: Checking filesystems under SliTaz 5

>Never check any partition if it is mounted

Nope. Never check read-write mounted partition.

So:

mount -o remount,ro /dev/sda3

e2fsck -n -f /dev/sda3

mount -o remount,rw /dev/sda3

yves04

Member

Registered: 2012-09-23

Posts: 135

Re: Checking filesystems under SliTaz 5

Ok devl547 you're right and it's more simple !

Escapetiger

Member

Registered: 2012-07-24

Posts: 44

Re: Checking filesystems under SliTaz 5

Many thank's for you :

@devl547

It works fine even if had to be directly connected with root (/dev/root / filesystem) to operate the "remount" of /home (to prevent "unable to ... filesystem busy").

The check returns "clean filesystem".

@yves04

I implement "tune2fs" with a try of 2 times (not appears at boot, not in "dmesg"), passed to 25 (like default rootfs), it seems to be OK too :-)

Escapetiger

Member

Registered: 2012-07-24

Posts: 44

Re: Checking filesystems under SliTaz 5

@yves04

"For 30 days before the next checking, use the command

tune2fs -c 30 /dev/sda3"

works fine, thank's again.

ps: I put it at the default 25 days value like the boot partition (see above), it appears at the boot screen (fastly !)and with the "dmesg" command too after

gibor

Moderator

Registered: 2011-04-30

Posts: 1,067

Re: Checking filesystems under SliTaz 5

Hi, if you want to get information on screen during check, put additional parameter “-C 0” on e2fsk

“e2fsck -n -f /dev/sda3”  transform to “e2fsck -C 0 -n -f /dev/sda3”

at boot during check view the progress bar

e2fsck 1.41.14 (22-Dec-2010)

Pass 1: Checking inodes, blocks, and sizes

/dev/sda8: |========================                                \ 42.3%