0
(09-01-2023, 13:55)dedito napisał(a): Na razie chce się dowiedzieć, która partycja przechodzi te sprawdzanie i z jakiego powodu jest sprawdzana co restart.
Kod:
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Tue Jan 3 10:07:22 2023
Last mount time: Tue Jan 10 11:32:05 2023
Last write time: Tue Jan 10 11:32:05 2023
Mount count: 53
Maximum mount count: -1
Last checked: Tue Jan 3 10:07:22 2023
Check interval: 0 (<none>)
Lifetime writes: 874 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
First orphan inode: 96208467
Default directory hash: half_md4
Directory Hash Seed: 73d576d6-b453-487a-8e7c-456194fbb990
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0x1c83edfe
tomasz@tomasz-O416:~$Dodano po pewnym czasie:
Kod:
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Tue Jan 3 10:30:59 2023
Last mount time: Tue Jan 10 11:32:04 2023
Last write time: Tue Jan 10 11:32:04 2023
Mount count: 51
Maximum mount count: -1
Last checked: Tue Jan 3 10:30:59 2023
Check interval: 0 (<none>)
Lifetime writes: 63 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
First orphan inode: 4195898
Default directory hash: half_md4
Directory Hash Seed: 98e5fe71-0bba-4cb8-9b38-d33a5b8ab84e
Journal backup: inode blocks
Checksum type: crc32c
Checksum: 0x1059c470
tomasz@tomasz-O416:~$