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
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
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
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-
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
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]
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
-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
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
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
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
-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
On 30 November 2014 at 23:49, Joel Roth wrote:
> On Sun, Nov 30, 2014 at 06:09:38PM +1100, Scott Ferguson wrote:
>> On 30 November 2014 at 17:47, Joel Roth wrote:
>> > I notice that /dev/sdb1, an ext4 partition on a USB drive has remounted
>> > read-only.
>> >
>> > I try
>> >
>> > umount /dev/sdb
On Sun, Nov 30, 2014 at 06:09:38PM +1100, Scott Ferguson wrote:
> On 30 November 2014 at 17:47, Joel Roth wrote:
> > I notice that /dev/sdb1, an ext4 partition on a USB drive has remounted
> > read-only.
> >
> > I try
> >
> > umount /dev/sdb1
> >
> > then
> >
> > fsck /dev/sdb1
> >
> > fsck from u
On 30 November 2014 at 17:47, Joel Roth wrote:
> I notice that /dev/sdb1, an ext4 partition on a USB drive has remounted
> read-only.
>
> I try
>
> umount /dev/sdb1
>
> then
>
> fsck /dev/sdb1
>
> fsck from util-linux 2.25.2
> e2fsck 1.42.12 (29-Aug-2014)
> /dev/sdb1 is in use.
> e2fsck: Cannot co
I notice that /dev/sdb1, an ext4 partition on a USB drive has remounted
read-only.
I try
umount /dev/sdb1
then
fsck /dev/sdb1
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/sdb1 is in use.
e2fsck: Cannot continue, aborting.
Is there a way that a volume can be in use without b
On Thu, Apr 12, 2007 at 07:55:52PM -0400, Edward J. Shornock wrote:
> Rick Pasotto wrote:
> >I have /home on a logical volume and recently expanded it. This morning
> >I started getting file system errors so I logged out, unmounted /home
> >and ran e2fsk on it. All seemed to be going normally but n
Rick Pasotto wrote:
I have /home on a logical volume and recently expanded it. This morning
I started getting file system errors so I logged out, unmounted /home
and ran e2fsk on it. All seemed to be going normally but now it has
*twice* displayed the following:
--
Pass 1: Checking inode
I have /home on a logical volume and recently expanded it. This morning
I started getting file system errors so I logged out, unmounted /home
and ran e2fsk on it. All seemed to be going normally but now it has
*twice* displayed the following:
--
Pass 1: Checking inodes, blocks, and sizes
G
On Sun, 08 Jan 2006, Debian User Leonard Chatagnier wrote:
On Fri, 06 Jan 2006, Henrique de Moraes Holschuh wrote:
>If you cannot, well, we are fixing the bug but it will take some time. The
>workaround that MAY work for you is to add TZ=ABC+XX:00 at the top of
>/etc/init.d/hwclockfirst.sh, wher
On Mon, 09 Jan 2006, Wayne Topa wrote:
> I think thats http://snapshot.debian.net, isn't it?
Yeah, sorry about that.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silic
Henrique de Moraes Holschuh([EMAIL PROTECTED]) is reported to have said:
> On Sun, 08 Jan 2006, Leonard Chatagnier wrote:
<-- snip -->
>
> http://snapshot.debian.org should be able to get you any version of any
> package in Debian you want. Try it, it should help you.
I think thats http://snapsh
Thanks Henrique, for the lessons in computer time and
some
of Debian's quirks. Coming from windows, was not
familiar with
acronyms UTC and RTC but some googling helped. And
thanks to Kent and
Robert for your imput.
The issue was resolved when I set clock to UTC with:
#date -u and set UTC=yes in /et
On Sun, 08 Jan 2006, Debian User Leonard Chatagnier wrote:
> On Fri, 06 Jan 2006, Henrique de Moraes Holschuh wrote:
> >If you cannot, well, we are fixing the bug but it will take some time. The
> >workaround that MAY work for you is to add TZ=ABC+XX:00 at the top of
> >/etc/init.d/hwclockfirst.sh
On Sun, 08 Jan 2006, Leonard Chatagnier wrote:
> e2fsprogs bug. No it's not; it's a glibc bug or a
> util-linux bug and maybe one or 2 more I don't
Util-linux is broken: It should run hwclockfirst.sh at S05 and S47. glibc
is broken, it should take care of /etc/localtime as a regular file or
hardl
On Sun, 08 Jan 2006, Debian User Leonard Chatagnier wrote:
> the list and the 2 related bug reports. But, being relatively new to Debian
> and linux, I don't know how. My time zone is CST, UTC-06. Time in KDE is
> set to CST and I can't find a way to change it. I did a 'date -u' to change
> clo
On Fri, 06 Jan 2006, Henrique de Moraes Holschuh wrote:
That may not fix it. Try setting your clock to UTC (and set UTC=yes in
/etc/default/rcS). If you can live with that, your Debian system will be
that much happier and stable, hardware clocks were meant to be always in
UTC, it's just old DO
try to create a folder called boot in your root sirectory and try to boot from there . Kent West <[EMAIL PROTECTED]> wrote: Leonard Chatagnier wrote:>I get these boot messages on a cold start or reboot>after doing an># aptitude upgrade -t testing that is still not>completely finished.>>Checking r
On Fri, 06 Jan 2006, Kent West wrote:
> >I get these boot messages on a cold start or reboot
> >after doing an
> ># aptitude upgrade -t testing that is still not
> >completely finished.
> >
> >Checking root file system
> >fsck 1.39-WIP(current date)
> >/dev/hda1: Superblock last write time in futur
Leonard Chatagnier wrote:
I get these boot messages on a cold start or reboot
after doing an
# aptitude upgrade -t testing that is still not
completely finished.
Checking root file system
fsck 1.39-WIP(current date)
/dev/hda1: Superblock last write time in future
I believe there was a thread
I get these boot messages on a cold start or reboot
after doing an
# aptitude upgrade -t testing that is still not
completely finished.
Checking root file system
fsck 1.39-WIP(current date)
/dev/hda1: Superblock last write time in future
/dev/hda1: UNEXPECTED INCONSISTENCY;run fsck MANUALLY
withou
On Thu, 11 Dec 2003, tripolar wrote:
> After compiling kernel, updated grub,then rebooted getting the following
> error
> ooops dont have it verbatim
> something about fsck failed
> /dev/hda6 doesnt exist or invalid
>
> use
> #mount -n -o remount,rw
>
Give the root password
and do fsck /dev/hda
After compiling kernel, updated grub,then rebooted getting the following
error
ooops dont have it verbatim
something about fsck failed
/dev/hda6 doesnt exist or invalid
use
#mount -n -o remount,rw
I hit ctrl-d hoping it would continue to boot but no such luck, rebooted
this time booted into old k
33 matches
Mail list logo
