LinHES Forums
http://forums.linhes.org/

R8 Hard drive house keeping
http://forums.linhes.org/viewtopic.php?f=23&t=23867
Page 1 of 1

Author:  TVBox [ Fri Nov 01, 2013 1:38 pm ]
Post subject:  R8 Hard drive house keeping

Is there any hard drive house keeping activities going on in R8? In the past I was under the understanding that the filesystems where checked after every 20 mounts.
Drive A is a SSD drive with my operating system (installed by R8) (Mount count 383)
Drive B is a 2TB backup drive (installed by using webmin) (Mount count 2 and 4)
Drive C is a 4TB drive for video / movies (installed by R8) (Mount Count 125)

Right now all the drives installed by R8 has a "Maximum mount count: -1"
The b drive that I installed by using Webmin
>>>Partition 1 "Maximum mount count: 25"
>>>Partition 2 "Maximum Mount count: 32" (I don't know why there is a difference here)

How do I fix this or is it not required any more? Is there anyone else seeing the same thing?

Code:
Drive A ++++++++++++++++++++++++++++++++
> dumpe2fs -h /dev/sda1 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              383
Maximum mount count:      -1

> dumpe2fs -h /dev/sda2 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sda2

> dumpe2fs -h /dev/sda3 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
dumpe2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3

> dumpe2fs -h /dev/sda5 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              383
Maximum mount count:      -1

> dumpe2fs -h /dev/sda6 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              383
Maximum mount count:      -1

> dumpe2fs -h /dev/sda7 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              383
Maximum mount count:      -1

Drive B +++++++++++++++++++++++++++++++++++++++++
> dumpe2fs -h /dev/sdb3 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              2
Maximum mount count:      25

dumpe2fs -h /dev/sdb4 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              4
Maximum Mount count:      32

Drive C +++++++++++++++++++++++++++++++++++++++++
> dumpe2fs -h /dev/sdc1 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              125
Maximum mount count:      -1


TVBox

Author:  RacerX [ Sat Nov 02, 2013 12:21 pm ]
Post subject:  Re: R8 Hard drive house keeping

Backup your ssd, copy the backup to drive B. Take a look at the sata cable on the drive. If you have any doubts replace it.

Smartmontools can check the health of your ssd

https://wiki.archlinux.org/index.php/S.M.A.R.T.

Author:  TVBox [ Sat Nov 02, 2013 9:20 pm ]
Post subject:  Re: R8 Hard drive house keeping

RacerX
you must see something that I don't. Can you elaborate.
I see that fsck is not running and that that should strike TERROR into the hearts of hard drive owners everywhere. Yes I know I am a couple of days late on that one.

Next has anyone else run the code below to see if they have Maximum mount count of -1?
Code:
dumpe2fs -h /dev/sda1 | grep -i 'mount count'

Off of the tune2fs man page
Code:
-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 corrupt 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.

So the "Maximum mount count: -1" means that the fsck file system check has been turned off for all R8 installed drives. There must a reason for doing this. Does anyone know of a alternate system to run the fsck check that is in play on R8?

I am aware that running fsck every twentieth boot at the beginning of the boot up cycle has always been a problem. It was solved by starting the system up five minutes before it was needed if you where running Mythwelcome. Today if you have a 4 Tera drive you would have to wait 50 minutes to boot up and that is only one drive. A couple of years ago there where discussions of moving the fsck check to the shutdown cycle.
>> Check number of mounts >> Shutdown >> if mount number high reboot >> run fsck >> Shutdown >>

If you know anything about this please feel free to share
TVBox

Author:  graysky [ Sun Nov 03, 2013 1:46 am ]
Post subject:  Re: R8 Hard drive house keeping

Does R8 use systemd for init? If so, that output (i.e. the -1) is normal based on my Arch workstation:

Code:
# dumpe2fs -h /dev/sdb1 | grep -i 'mount co'
dumpe2fs 1.42.8 (20-Jun-2013)
Mount count:              3
Maximum mount count:      -1


Systemd must handle the fsck'ing although in your case given those high numbers, I wonder if it's not.

Author:  TVBox [ Mon Nov 04, 2013 3:52 pm ]
Post subject:  Re: R8 Hard drive house keeping

Could someone with a clean install of R8-02-11-2013.iso (no database / backup carried forward) on a GPT EXT4 partition check there mount count because it isn't very likely that I can be the only one here.

Also what is the arch equivalent to the code below.
Code:
> shutdown -rF now
/sbin/shutdown: illegal option -- F


I want to reboot and run check disk

So far below this is just a stab in the dark - I don't know if it means anything.

Code:
> grep fsck /etc/rc.sysinit
if [[ ! -e /run/initramfs/root-fsck ]]; then
   # remount root ro to allow for fsck later on, we remount now to
run_hook sysinit_prefsck
if [[ -x $(type -P fsck) ]]; then
      fsck_all >|"${FSCK_OUT:-/dev/stdout}" 2>|"${FSCK_ERR:-/dev/stdout}"
   declare -r fsckret=$?
   (( fsckret <= 1 )) && stat_done || stat_fail
   declare -r fsckret=0
run_hook sysinit_postfsck
fsck_reboot $fsckret


TVBox

Author:  heilig [ Thu Nov 07, 2013 1:46 am ]
Post subject:  Re: R8 Hard drive house keeping

TVBox wrote:
Could someone with a clean install of R8-02-11-2013.iso (no database / backup carried forward) on a GPT EXT4 partition check there mount count because it isn't very likely that I can be the only one.


My filesystems are ext3 and xfs, but it is a clean install of R8.

FWIW:
Code:
> dumpe2fs -h /dev/sda1 | grep -i 'mount count'
dumpe2fs 1.42.4 (12-June-2012)
Mount count:              59
Maximum mount count:      -1


sda5 and sda6 are the same.

Personally I don't mind that there is no automatic check on boot, at least for the data partitions. The time this took ruined a number of recordings. I switched to xfs a couple of years ago and had no more problems since then.

For R8 I am considering ext4, though. I am still on 6.04, my R8 box is just for testing so far.

Jens

Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/