On Wed, 27 Mar 2024 19:51, Carlos E. R. <> wrote:
On Wednesday, 2024-03-27 at 19:38 +0100, Carlos E. R. wrote:
On 2024-03-27 18:17, Yamaban via openSUSE Users wrote:
On Wed, 27 Mar 2024 14:09, Andrei Borzenkov <> wrote:
On Wed, Mar 27, 2024 at 4:04 PM Andrei Borzenkov <> wrote:
On Wed, Mar 27, 2024 at 3:41 PM Carlos E. R. <> wrote:
1. Thanks for the link to the notes. 2. Hmm, just checked a drive that was formatted using Leap 42.1 (Kernel 4.1.39 , xfsprogs-3.2.1) and xfs_info /mnt/point showed a "crc=1"
... so, safe if done in Leap 42.1 with std-options, but, for safety, check yourself with "xfs_info"
Telcontar:~ # xfs_info /data/storage_d meta-data=/dev/sdd2 isize=512 agcount=4, agsize=52188544 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=0, rmapbt=0 = reflink=0 bigtime=0 inobtcount=0 data = bsize=4096 blocks=208754176, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=101930, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Telcontar:~ #
<snip log>
According to this, partition /data/storage_d is fine. But it is not, the log also says:
<0.4> 2024-03-27T11:19:01.689438+01:00 Telcontar kernel - - - [ 11.438732][ T1003] xfs filesystem being mounted at /data/storage_d supports timestamps until 2038 (0x7fffffff)
So, I want to correct this, which is not mentioned in the notes I have read so far.
Yeah, ok, there is a over decade till then, but till then I will see noise in the /var/log/war log which I don't want to see.
to quote from your own xfs_info call for /data/storage_d: ... bigtime=0 THAT is the cause of the "timestamps until 2038" noise. - Yamaban.