[arch-general] Strange and annoying causing issues
Hi folks Most the time the system is spot ion thanks Arch Linux but every now and then i get something that is causing consternation one of those times is now i am getting this filling dmesg 23.113873] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 23.114081] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.125584] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.127583] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 23.719265] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 23.719777] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.730310] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.732198] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff)[ 26.246319] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/private/systemd/journal-upload supports timestamps until 2038 (0x7fffffff) [ 26.253998] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/private/systemd/journal-upload supports timestamps until 2038 (0x7fffffff) [ 26.254017] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 26.272915] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/private/systemd/journal-upload supports timestamps until 2038 (0x7fffffff) [ 26.273523] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 79.301218] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/upower supports timestamps until 2038 (0x7fffffff) [ 79.301364] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 79.318565] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/upower supports timestamps until 2038 (0x7fffffff) [ 79.319569] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) it is causing issues as far as i can make out on the USB Camera i get a pile of the above scroll up and the camera dies the camera is Bus 002 Device 002: ID 23c5:1478 Xiongmai web camera it works very well good clear video untill this lot started now it dies all the time in the middle of streaming (Discord) Thanks . Pete Pete
On Sun, 12 Dec 2021 at 10:59, pete via arch-general <arch-general@lists.archlinux.org> wrote:
Hi folks
Most the time the system is spot ion thanks Arch Linux but every now and then i get something that is causing consternation one of those times is now i am getting this filling dmesg
23.113873] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 23.114081] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.125584] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.127583] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 23.719265] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 23.719777] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.730310] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/tor supports timestamps until 2038 (0x7fffffff) [ 23.732198] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff)[ 26.246319] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/private/systemd/journal-upload supports timestamps until 2038 (0x7fffffff) [ 26.253998] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/private/systemd/journal-upload supports timestamps until 2038 (0x7fffffff) [ 26.254017] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 26.272915] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/private/systemd/journal-upload supports timestamps until 2038 (0x7fffffff) [ 26.273523] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 79.301218] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/upower supports timestamps until 2038 (0x7fffffff) [ 79.301364] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) [ 79.318565] xfs filesystem being remounted at /run/systemd/unit-root/var/lib/upower supports timestamps until 2038 (0x7fffffff) [ 79.319569] xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff)
it is causing issues as far as i can make out on the USB Camera i get a pile of the above scroll up and the camera dies
the camera is Bus 002 Device 002: ID 23c5:1478 Xiongmai web camera it works very well good clear video untill this lot started now it dies all the time in the middle of streaming (Discord)
Thanks .
Pete
Pete
It seems you messed up with your filesystems and mount points. I don't know much about XFS, but I'm pretty sure that a mount point named "tmp" should have tmpfs, not xfs. Regards, Neven
On Sun, 12 Dec 2021 14:04:44 +0000, Neven Sajko via arch-general wrote:
I'm pretty sure that a mount point named "tmp" should have tmpfs
Hi, not necessarily, see https://wiki.archlinux.org/title/tmpfs#Disable_automatic_mount Regards, Ralf
On Sun, 12 Dec 2021 15:36:55 +0100 Ralf Mardorf via arch-general <arch-general@lists.archlinux.org> wrote:
On Sun, 12 Dec 2021 14:04:44 +0000, Neven Sajko via arch-general wrote:
I'm pretty sure that a mount point named "tmp" should have tmpfs
Hi,
not necessarily, see https://wiki.archlinux.org/title/tmpfs#Disable_automatic_mount
Regards, Ralf
Thank you Ralf i will try that hope it solves the issue as for messing up the filesystem i have not done anything apart from updtaes via " pacman -Syu" for a good few weeks . Cheers Pete
On Sun, 12 Dec 2021 23:41:49 +0000, pete via arch-general wrote:
On Sun, 12 Dec 2021 15:36:55 +0100 Ralf Mardorf via arch-general <arch-general@lists.archlinux.org> wrote:
On Sun, 12 Dec 2021 14:04:44 +0000, Neven Sajko via arch-general wrote:
I'm pretty sure that a mount point named "tmp" should have tmpfs
Hi,
not necessarily, see https://wiki.archlinux.org/title/tmpfs#Disable_automatic_mount
Regards, Ralf
Thank you Ralf i will try that hope it solves the issue as for messing up the filesystem i have not done anything apart from updtaes via " pacman -Syu" for a good few weeks .
Hi, I don't think it's related to the issue. [root@archlinux rocketmouse]# df -h -t tmpfs Filesystem Size Used Avail Use% Mounted on run 7.6G 1.4M 7.6G 1% /run tmpfs 7.6G 192K 7.6G 1% /dev/shm tmpfs 7.6G 4.3M 7.6G 1% /tmp tmpfs 1.6G 56K 1.6G 1% /run/user/1000 https://wiki.archlinux.org/title/tmpfs#Usage I only wanted to point out, that "tmp" where ever located, e.g. even /tmp, not necessarily is tmpfs. Better take a look at https://www.google.de/search?q=arch+linux+%22filesystem+being+remounted%22+%... At least the timestamp part is unimportant. "I can't off hand help with the remounting problem, but the timestamps message is due to https://en.wikipedia.org/wiki/Year_2038_problem." - https://forums.centos.org/viewtopic.php?t=73195#p307936 However, a lot of "filesystem being remounted" hits by the above Google search are related to xfs. I didn't read the hits, so I don't know if one of those hits is related to your issue. Regards, Ralf
| > /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) | > | > it is causing issues as far as i can make out on the USB Camera i get a pile | > of the above scroll up and the camera dies | > | > the camera is | > Bus 002 Device 002: ID 23c5:1478 Xiongmai web camera it works very well good | > clear video untill this lot started now it dies all the time in the middle of | > streaming (Discord) | > The part about the timestamps is a normal warning with XFS (there is an option to format with 64 bit timestamps but I seem to recall it being flakey somehow) It might be worth checking or repairing your drive to see if that fixes your camera issue, see: https://wiki.archlinux.org/title/XFS#Repair (you might need to install `xfsprogs`) See what changes would be made (without making any actual changes): xfs_repair -n /dev/sdX1 -t 120 "If the journal log has become corrupted, you can reset the log by specifying the -L option to xfs_repair." Warning: "The xfs_repair utility cannot repair an XFS file system with a dirty log. To clear the log, mount and unmount the XFS file system. If the log is corrupt and cannot be replayed, use the -L option ("force log zeroing") to clear the log, that is, xfs_repair -L /dev/device. Be aware that this may result in further corruption or data loss." xfs_repair -L /dev/sdX1 -t 120 Brett.
On 12/13/21 12:27 AM, brettm via arch-general wrote:
The part about the timestamps is a normal warning with XFS (there is an option to format with 64 bit timestamps but I seem to recall it being flakey somehow)
The XFS bigtime features isn't at all flakey. (I've been using it for months without any issue.) But it used to print out an "experimental" feature warning. They removed that warning a few months ago, as the feature had been merged in over a year ago and has had no major issues reported. DR
On Mon, 13 Dec 2021 11:16:50 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/13/21 12:27 AM, brettm via arch-general wrote:
The part about the timestamps is a normal warning with XFS (there is an option to format with 64 bit timestamps but I seem to recall it being flakey somehow)
The XFS bigtime features isn't at all flakey. (I've been using it for months without any issue.) But it used to print out an "experimental" feature warning. They removed that warning a few months ago, as the feature had been merged in over a year ago and has had no major issues reported.
DR
Ahhh there may be my problem I still gt the experimental warning every now and then have to try forced update of all XFS related progs Pete .
On 12/13/21 2:30 PM, pete via arch-general wrote:
On Mon, 13 Dec 2021 11:16:50 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/13/21 12:27 AM, brettm via arch-general wrote:
The part about the timestamps is a normal warning with XFS (there is an option to format with 64 bit timestamps but I seem to recall it being flakey somehow)
The XFS bigtime features isn't at all flakey. (I've been using it for months without any issue.) But it used to print out an "experimental" feature warning. They removed that warning a few months ago, as the feature had been merged in over a year ago and has had no major issues reported.
DR
Ahhh there may be my problem
I still gt the experimental warning every now and then have to try forced update of all XFS related progs
You shouldn't be seeing the experimental warning any more if you're running up to date kernels. It got removed around August. (https://www.spinics.net/lists/linux-xfs/msg54740.html) DR
On Mon, 13 Dec 2021 15:00:28 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/13/21 2:30 PM, pete via arch-general wrote:
On Mon, 13 Dec 2021 11:16:50 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/13/21 12:27 AM, brettm via arch-general wrote:
The part about the timestamps is a normal warning with XFS (there is an option to format with 64 bit timestamps but I seem to recall it being flakey somehow)
The XFS bigtime features isn't at all flakey. (I've been using it for months without any issue.) But it used to print out an "experimental" feature warning. They removed that warning a few months ago, as the feature had been merged in over a year ago and has had no major issues reported.
DR
Ahhh there may be my problem
I still gt the experimental warning every now and then have to try forced update of all XFS related progs
You shouldn't be seeing the experimental warning any more if you're running up to date kernels. It got removed around August. (https://www.spinics.net/lists/linux-xfs/msg54740.html)
DR
Hi . Wonder why then because i update almost daily with " pacman -Syu" the only thing i am cautcious of is messa as it can cause problems in some programs for me . Pete
On 12/14/21 8:27 AM, pete via arch-general wrote:
On Mon, 13 Dec 2021 15:00:28 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/13/21 2:30 PM, pete via arch-general wrote:
I still gt the experimental warning every now and then have to try forced update of all XFS related progs
You shouldn't be seeing the experimental warning any more if you're running up to date kernels. It got removed around August. (https://www.spinics.net/lists/linux-xfs/msg54740.html)
DR
Hi .
Wonder why then because i update almost daily with " pacman -Syu" the only thing i am cautcious of is messa as it can cause problems in some programs for me .
Mirror (very) out of date?
On Tue, 14 Dec 2021 09:32:55 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/14/21 8:27 AM, pete via arch-general wrote:
On Mon, 13 Dec 2021 15:00:28 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/13/21 2:30 PM, pete via arch-general wrote:
I still gt the experimental warning every now and then have to try forced update of all XFS related progs
You shouldn't be seeing the experimental warning any more if you're running up to date kernels. It got removed around August. (https://www.spinics.net/lists/linux-xfs/msg54740.html)
DR
Hi .
Wonder why then because i update almost daily with " pacman -Syu" the only thing i am cautcious of is messa as it can cause problems in some programs for me .
Mirror (very) out of date?
So why am i still seeing this then as i say i update the system virtually every day it makes no sense Pete .
On 12/14/21 11:32 AM, pete via arch-general wrote:
So why am i still seeing this then
as i say i update the system virtually every day it makes no sense
You are seeing this message in your dmesg / journalctl? "EXPERIMENTAL big timestamp feature in use. Use at your own risk!" Are you using the LTS kernel? DR
On Tue, 14 Dec 2021 12:10:40 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/14/21 11:32 AM, pete via arch-general wrote:
So why am i still seeing this then
as i say i update the system virtually every day it makes no sense
You are seeing this message in your dmesg / journalctl?
"EXPERIMENTAL big timestamp feature in use. Use at your own risk!"
Are you using the LTS kernel?
DR
Hi . I see this once booted after i log in to a tty i do not start into a graphical enviroment i prefer old school then startx I see the message in the tty Pete
So it seems that you are using an old LTS kernel, try do "sudo pacman -S linux" and when asked remove linux-lts. If you aren't using LTS, try to update your mirrors. On 16 December 2021 00:43:06 GMT, pete via arch-general <arch-general@lists.archlinux.org> wrote:
On Tue, 14 Dec 2021 12:10:40 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/14/21 11:32 AM, pete via arch-general wrote:
So why am i still seeing this then
as i say i update the system virtually every day it makes no sense
You are seeing this message in your dmesg / journalctl?
"EXPERIMENTAL big timestamp feature in use. Use at your own risk!"
Are you using the LTS kernel?
DR
Hi . I see this once booted after i log in to a tty i do not start into a graphical enviroment i prefer old school then startx
I see the message in the tty
Pete
Am 20.12.21 um 09:44 schrieb KSP Atlas via arch-general:
So it seems that you are using an old LTS kernel, try do "sudo pacman -S linux" and when asked remove linux-lts. If you aren't using LTS, try to update your mirrors.
At least I'm getting xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) also on 5.15.x Kind Regards Bjoern
On 12/20/21 3:51 AM, Bjoern Franke via arch-general wrote:
At least I'm getting xfs filesystem being remounted at /run/systemd/unit-root/var/tmp supports timestamps until 2038 (0x7fffffff) also on 5.15.x
Kind Regards Bjoern
That's a different message. That means that your filesystem is *not* using the bigtime feature, and so will experience an issue with dates further forward than 2038. (See https://en.wikipedia.org/wiki/Year_2038_problem) To switch the xfs file system to use bigtime, see the instructions here: https://wiki.archlinux.org/title/XFS#Big_timestamps (Note that the file system has to be unmounted when you make the conversion.) DR
On Mon, 20 Dec 2021 08:44:57 +0000 KSP Atlas via arch-general <arch-general@lists.archlinux.org> wrote:
So it seems that you are using an old LTS kernel, try do "sudo pacman -S linux" and when asked remove linux-lts. If you aren't using LTS, try to update your mirrors.
On 16 December 2021 00:43:06 GMT, pete via arch-general <arch-general@lists.archlinux.org> wrote:
On Tue, 14 Dec 2021 12:10:40 -0500 David Rosenstrauch via arch-general <arch-general@lists.archlinux.org> wrote:
On 12/14/21 11:32 AM, pete via arch-general wrote:
So why am i still seeing this then
as i say i update the system virtually every day it makes no sense
You are seeing this message in your dmesg / journalctl?
"EXPERIMENTAL big timestamp feature in use. Use at your own risk!"
Are you using the LTS kernel?
DR
Hi . I see this once booted after i log in to a tty i do not start into a graphical enviroment i prefer old school then startx
I see the message in the tty
Pete
Hi nope latest kernel updated daily " pacman -S linux warning: linux-5.15.10.arch1-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Packages (1) linux-5.15.10.arch1-1 Total Installed Size: 135.25 MiB Net Upgrade Size: 0.00 MiB . " this is getting silly now Cheers Pete
| On 12/13/21 12:27 AM, brettm via arch-general wrote: | > The part about the timestamps is a normal warning with XFS (there is an option to format with 64 bit timestamps but I seem to recall it being flakey somehow) | | The XFS bigtime features isn't at all flakey. (I've been using it for | months without any issue.) But it used to print out an "experimental" | feature warning. They removed that warning a few months ago, as the | feature had been merged in over a year ago and has had no major issues | reported. | After I wrote that email, I remembered what the problem was. It wasn't flakeyness. A drive formatted on Arch Linux with XFS 64-bit timestamps was unable to be mounted on my spare laptop running Linux Mint. I didn't look any further into the issue, just used 32-bit timestamps. Somehow I doubt I'll still be using this drive in the year 2038... Brett.
participants (7)
-
Bjoern Franke
-
brettm
-
David Rosenstrauch
-
KSP Atlas
-
Neven Sajko
-
pete
-
Ralf Mardorf