Your message dated Fri, 30 Sep 2016 17:13:07 -0400
with message-id <[email protected]>
and subject line Re: Bug#839255: fsck boot messages really should be stored
somewhere
has caused the Debian Bug report #839255,
regarding fsck boot messages really should be stored somewhere
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
839255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839255
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.43.3-1
Severity: wishlist
1. Storm hits, power fails.
2. When power restored, boot computer. Notice some messages about clearing
orphaned inodes fly by.
3. Now check for any place on the computer where those messages might be stored.
# find /var/log -type f -mtime -1|xargs zgrep -i inode
/var/log/kern.log:Oct 1 02:42:10 jidanni5 kernel: [ 0.000000] Inode-cache
hash table entries: 65536 (order: 6, 262144 bytes)
/var/log/syslog:Oct 1 02:42:10 jidanni5 kernel: [ 0.000000] Inode-cache
hash table entries: 65536 (order: 6, 262144 bytes)
/var/log/messages:Oct 1 02:42:10 jidanni5 kernel: [ 0.000000] Inode-cache
hash table entries: 65536 (order: 6, 262144 bytes)
I.e., no not there.
I bet even the Linux experts have no way to see these messages later
(without attaching a second printing(!) terminal.)
Can't there be a tiny place in the gigabytes of memory these days, where
initramfs messages, the same ones we see flying by upon boot,
are stored, and then, after the system is fully running, write those
messages to a file in /var/log?
Please reassign this bug (after adding ideas) to (probably ?) the kernel.
Semi/related/older projects:
$ dlocate /var/log/fsck
initscripts: /var/log/fsck
$ ls -l /var/log/fsck
total 8
-rw-r----- 1 root adm 122 2014-07-12 checkfs
-rw-r----- 1 root adm 200 2014-07-12 checkroot
I.e., stopped working years ago.
$ dlocate bootlog
initscripts: /etc/init.d/bootlogs
systemd: /lib/systemd/system/bootlogd.service
systemd: /lib/systemd/system/bootlogs.service
systemd: /lib/systemd/system/stop-bootlogd-single.service
systemd: /lib/systemd/system/stop-bootlogd.service
which I recall won't help in this case either.
-- System Information:
Debian Release: stretch/sid
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.7.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.43.3-1
ii libblkid1 2.28.2-1
ii libc6 2.24-3
ii libcomerr2 1.43.3-1
ii libss2 1.43.3-1
ii libuuid1 2.28.2-1
ii util-linux 2.28.2-1
e2fsprogs recommends no packages.
Versions of packages e2fsprogs suggests:
pn e2fsck-static <none>
pn fuse2fs <none>
pn gpart <none>
ii parted 3.2-15
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, Oct 01, 2016 at 03:12:06AM +0800, 積丹尼 Dan Jacobson wrote:
>
> I bet even the Linux experts have no way to see these messages later
> (without attaching a second printing(!) terminal.)
You'd lose that bet. A quick Google search turns up:
https://lists.debian.org/debian-user/2014/05/msg00689.html
And the magic is:
journalctl -b | grep systemd-fsck
> Please reassign this bug (after adding ideas) to (probably ?) the kernel.
Not, this is a userspace issue. Specifically, it's up to the init
system.
> Semi/related/older projects:
>
> $ dlocate /var/log/fsck
> initscripts: /var/log/fsck
> $ ls -l /var/log/fsck
> total 8
> -rw-r----- 1 root adm 122 2014-07-12 checkfs
> -rw-r----- 1 root adm 200 2014-07-12 checkroot
> I.e., stopped working years ago.
It stopped working when Debian transitioned from using System V init
scripts and moved to systemd.
Systemd has its own logging system. Please do some reading about
journalctl and systemctl.
- Ted
--- End Message ---
