Re: fsck fails to check?

2015-07-23 Thread Ralph Katz
On 07/23/2015 03:07 PM, David Wright wrote: > Quoting Ralph Katz (ralph.k...@rcn.com): >> So I assumed setting the time interval would force a check on the next >> reboot. syslog shows check not done: >> And again, from tune2fs -l /dev/sda1 >> Last mount time: Thu Jul 23 10:45:36 2015

Re: fsck fails to check?

2015-07-23 Thread Ralph Katz
On 07/23/2015 02:20 PM, Jape Person wrote: > On 07/23/2015 01:48 PM, Ralph Katz wrote: >> So the question is, how to set a time interval that actually forces a >> check as suggested my man tune2fs quoted above? Or is this a bug? > My sincere apologies for accidentally sending an earlier message

Re: fsck fails to check?

2015-07-23 Thread Jape Person
On 07/23/2015 02:52 PM, David Wright wrote: Quoting Jape Person (jap...@comcast.net): On 07/23/2015 12:59 PM, David Wright wrote: Quoting Ralph Katz (ralph.k...@rcn.com): Yesterday I learned (from this list) that apparently Debian now defaults to no periodic disk checks after file system insta

Re: fsck fails to check?

2015-07-23 Thread David Wright
Quoting Ralph Katz (ralph.k...@rcn.com): > On 07/23/2015 12:59 PM, David Wright wrote: > > > Yes, you missed yesterday's posting: > > > > https://lists.debian.org/debian-user/2015/07/msg00977.html > > I saw it, but perhaps I don't understand it. > > From man tune2fs: > > >-i interval-

Re: fsck fails to check?

2015-07-23 Thread David Wright
Quoting Jape Person (jap...@comcast.net): > On 07/23/2015 12:59 PM, David Wright wrote: > >Quoting Ralph Katz (ralph.k...@rcn.com): > >>Yesterday I learned (from this list) that apparently Debian now defaults > >>to no periodic disk checks after file system installation. So I > >>manually added on

Re: fsck fails to check?

2015-07-23 Thread Jape Person
On 07/23/2015 01:48 PM, Ralph Katz wrote: On 07/23/2015 12:59 PM, David Wright wrote: Yes, you missed yesterday's posting: https://lists.debian.org/debian-user/2015/07/msg00977.html I saw it, but perhaps I don't understand it. From man tune2fs: -i interval-between-checks[d|m|w]

Re: fsck fails to check?

2015-07-23 Thread Ralph Katz
On 07/23/2015 12:59 PM, David Wright wrote: > Yes, you missed yesterday's posting: > > https://lists.debian.org/debian-user/2015/07/msg00977.html I saw it, but perhaps I don't understand it. From man tune2fs: >-i interval-between-checks[d|m|w] > Adjust the maximal time b

Re: fsck fails to check?

2015-07-23 Thread Ralph Katz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/23/2015 11:28 AM, David Guyot wrote: > Le jeudi 23 juillet 2015 à 11:24 -0400, Ralph Katz a écrit : >> So I manually added one yesterday. > What does that mean? Did you add a /forcefsck file? No. Yesterday I did: sudo tune2fs -i 180 /dev/sda1

Re: fsck fails to check?

2015-07-23 Thread Jape Person
On 07/23/2015 12:59 PM, David Wright wrote: Quoting Ralph Katz (ralph.k...@rcn.com): Yesterday I learned (from this list) that apparently Debian now defaults to no periodic disk checks after file system installation. So I manually added one yesterday. Yet when I rebooted after today's kernel u

Re: fsck fails to check?

2015-07-23 Thread David Wright
Quoting Ralph Katz (ralph.k...@rcn.com): > Yesterday I learned (from this list) that apparently Debian now defaults > to no periodic disk checks after file system installation. So I > manually added one yesterday. > > Yet when I rebooted after today's kernel update, no check was forced on > the u

Re: fsck fails to check?

2015-07-23 Thread David Guyot
Le jeudi 23 juillet 2015 à 11:24 -0400, Ralph Katz a écrit : > So I manually added one yesterday. What does that mean? Did you add a /forcefsck file? Regards. -- David Guyot Administrateur système, réseau et télécom / Sysadmin Europe Camions Interactive / Stockway Moulin Collot F-88500 Ambacourt

fsck fails to check?

2015-07-23 Thread Ralph Katz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Yesterday I learned (from this list) that apparently Debian now defaults to no periodic disk checks after file system installation. So I manually added one yesterday. Yet when I rebooted after today's kernel update, no check was forced on the up-to