On Tue, 29 Nov 2016, Michael Biebl wrote:
Am 29.11.2016 um 08:40 schrieb Pierre Frenkiel:
For example, how do you explain the presence in syslog of 12 times
the same 12 lines?
The lines you posted are not the same. They are for different mount points.
--
Why is it that all of the instru
Am 29.11.2016 um 08:40 schrieb Pierre Frenkiel:
> For example, how do you explain the presence in syslog of 12 times
> the same 12 lines?
The lines you posted are not the same. They are for different mount points.
--
Why is it that all of the instruments seeking intelligent life in the
univ
On Tue, 29 Nov 2016, Michael Biebl wrote:
Am 28.11.2016 um 19:35 schrieb Pierre Frenkiel:
It seems that one must not be too curious, as each time you dig too
deep, you find some kind of mystery.
On the contrary, I think this is what makes Linux great. There might be
things which are a myste
Am 28.11.2016 um 19:35 schrieb Pierre Frenkiel:
> It seems that one must not be too curious, as each time you dig too
> deep, you find some kind of mystery.
On the contrary, I think this is what makes Linux great. There might be
things which are a mystery to you at first, but you are allowed to
On Mon, 28 Nov 2016, Michael Biebl wrote:
Oh, this is quite simple to explain.
If your file system is clean, fsck will simply do nothing.
The "Last checked" attribute is only reset, if fsck is actually run due to
1/ unclean file system
2/ forced fsck (fsck.mode=force on the kernel command line)
Am 28.11.2016 um 15:10 schrieb Pierre Frenkiel:
> On Mon, 28 Nov 2016, Michael Biebl wrote:
> thank you for this usefull information, but some inconsistency remains:
>
> in /run/initramfs/fsck.log, I find:
>
> Log of fsck -C -a -V -t ext4 /dev/sda2
> Sat Nov 26 06:53:12 2016
>
>
On Mon, 28 Nov 2016, Michael Biebl wrote:
/ and /usr are fscked by the initramfs.
Assuming you use initramfs-tools, which is the default in Debian, you
can find the log files at
/run/initramfs/fsck*
thank you for this usefull information, but some inconsistency remains:
in /run/initramfs/f
Am 28.11.2016 um 14:11 schrieb Richard Hector:
> On 26/11/16 22:03, Pierre Frenkiel wrote:
>> According the tune2fs output, the check on / was actually done.
>> I naïvely looked at syslog to find the checked devices, and I
>> could not imagine
>> that the fsck checks are reported in
On Tue, 29 Nov 2016, Richard Hector wrote:
On 26/11/16 22:03, Pierre Frenkiel wrote:
According the tune2fs output, the check on / was actually done.
I naïvely looked at syslog to find the checked devices, and I
could not imagine
that the fsck checks are reported in syslog for al
On 26/11/16 22:03, Pierre Frenkiel wrote:
> According the tune2fs output, the check on / was actually done.
> I naïvely looked at syslog to find the checked devices, and I
> could not imagine
> that the fsck checks are reported in syslog for all partitions, but
> not for /...
Becau
On Wed, 23 Nov 2016, David Wright wrote:
As for the root filesystem, are you saying that it was not checked
even when you did what I suggested? What does
# tune2fs -l /dev/sda1 | grep 'st ch'
show (assuming / is /dev/sda1)?
hi David,
I said "inconsistency, but I must add "behaviour imposs
On Tue 22 Nov 2016 at 23:32:34 (+0100), Pierre Frenkiel wrote:
> On Tue, 22 Nov 2016, David Wright wrote:
>
> >Some things got a bit out-of-date perhaps. What works is to edit the
> >linux line in grub, adding [forcefsck]
> It would be interesting to know which one is out-of-date, checkfs.sh or
On Tue, 22 Nov 2016, David Wright wrote:
Some things got a bit out-of-date perhaps. What works is to edit the
linux line in grub, adding
Hi David,
It would be interesting to know which one is out-of-date, checkfs.sh or
systemd-fsck?
Anyway, my question was not "how to force fsck". This
On Tue 22 Nov 2016 at 19:50:50 (+0100), Pierre Frenkiel wrote:
> trying to force the exec of fsck at boot, I found in init.d/checkfs.sh:
>
> if [ -f /forcefsck ] || grep -q -s -w -i "forcefsck" /proc/cmdline
> then
> force="-f"
> else
>
hi everybody,
trying to force the exec of fsck at boot, I found in init.d/checkfs.sh:
if [ -f /forcefsck ] || grep -q -s -w -i "forcefsck" /proc/cmdline
then
force="-f"
else
force=""
fi
So, I t
15 matches
Mail list logo
