Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Plein d'erreurs EXT4 : c'est mon disque dur? [réponse: en fait non]

®om

Salut,

Comme je l'ai indiqué dans ce bug report, j'ai plein de segfaults, qui pourraient provenir d'erreurs EXT4 :

$ grep EXT4 /var/log/syslog
Mar 28 12:23:10 rom-laptop kernel: [    3.229656] EXT4-fs: barriers enabled
Mar 28 12:23:10 rom-laptop kernel: [    3.235747] EXT4-fs: delayed allocation enabled
Mar 28 12:23:10 rom-laptop kernel: [    3.235748] EXT4-fs: file extents enabled
Mar 28 12:23:10 rom-laptop kernel: [    3.237283] EXT4-fs: mballoc enabled
Mar 28 12:23:10 rom-laptop kernel: [    3.237287] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 12:23:10 rom-laptop kernel: [    7.526737] EXT4 FS on sda1, internal journal on sda1:8
Mar 28 12:23:10 rom-laptop kernel: [    8.245886] EXT4-fs: barriers enabled
Mar 28 12:23:10 rom-laptop kernel: [    8.246618] EXT4 FS on sda6, internal journal on sda6:8
Mar 28 12:23:10 rom-laptop kernel: [    8.246620] EXT4-fs: delayed allocation enabled
Mar 28 12:23:10 rom-laptop kernel: [    8.246622] EXT4-fs: file extents enabled
Mar 28 12:23:10 rom-laptop kernel: [    8.266576] EXT4-fs: mballoc enabled
Mar 28 12:23:10 rom-laptop kernel: [    8.266580] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 12:30:31 rom-laptop kernel: [    3.301260] EXT4-fs: barriers enabled
Mar 28 12:30:31 rom-laptop kernel: [    3.309855] EXT4-fs: delayed allocation enabled
Mar 28 12:30:31 rom-laptop kernel: [    3.309856] EXT4-fs: file extents enabled
Mar 28 12:30:31 rom-laptop kernel: [    3.311379] EXT4-fs: mballoc enabled
Mar 28 12:30:31 rom-laptop kernel: [    3.311383] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 12:30:31 rom-laptop kernel: [    7.706410] EXT4 FS on sda1, internal journal on sda1:8
Mar 28 12:30:31 rom-laptop kernel: [    8.429074] EXT4-fs: barriers enabled
Mar 28 12:30:31 rom-laptop kernel: [    8.429865] EXT4 FS on sda6, internal journal on sda6:8
Mar 28 12:30:31 rom-laptop kernel: [    8.429868] EXT4-fs: delayed allocation enabled
Mar 28 12:30:31 rom-laptop kernel: [    8.429869] EXT4-fs: file extents enabled
Mar 28 12:30:31 rom-laptop kernel: [    8.449813] EXT4-fs: mballoc enabled
Mar 28 12:30:31 rom-laptop kernel: [    8.449816] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 11:38:51 rom-laptop kernel: [    3.202641] EXT4-fs: barriers enabled
Mar 28 11:38:51 rom-laptop kernel: [    3.208782] EXT4-fs: delayed allocation enabled
Mar 28 11:38:51 rom-laptop kernel: [    3.208783] EXT4-fs: file extents enabled
Mar 28 11:38:51 rom-laptop kernel: [    3.210301] EXT4-fs: mballoc enabled
Mar 28 11:38:51 rom-laptop kernel: [    3.210304] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 11:38:51 rom-laptop kernel: [    8.296542] EXT4 FS on sda1, internal journal on sda1:8
Mar 28 11:38:51 rom-laptop kernel: [    8.985795] EXT4-fs: barriers enabled
Mar 28 11:38:51 rom-laptop kernel: [    8.986520] EXT4 FS on sda6, internal journal on sda6:8
Mar 28 11:38:51 rom-laptop kernel: [    8.986522] EXT4-fs: delayed allocation enabled
Mar 28 11:38:51 rom-laptop kernel: [    8.986524] EXT4-fs: file extents enabled
Mar 28 11:38:51 rom-laptop kernel: [    9.006446] EXT4-fs: mballoc enabled
Mar 28 11:38:51 rom-laptop kernel: [    9.006450] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 11:49:43 rom-laptop kernel: [    3.132294] EXT4-fs: barriers enabled
Mar 28 11:49:43 rom-laptop kernel: [    3.138421] EXT4-fs: delayed allocation enabled
Mar 28 11:49:43 rom-laptop kernel: [    3.138423] EXT4-fs: file extents enabled
Mar 28 11:49:43 rom-laptop kernel: [    3.139945] EXT4-fs: mballoc enabled
Mar 28 11:49:43 rom-laptop kernel: [    3.139949] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 11:49:43 rom-laptop kernel: [    8.217937] EXT4 FS on sda1, internal journal on sda1:8
Mar 28 11:49:43 rom-laptop kernel: [    8.915939] EXT4-fs: barriers enabled
Mar 28 11:49:43 rom-laptop kernel: [    8.916666] EXT4 FS on sda6, internal journal on sda6:8
Mar 28 11:49:43 rom-laptop kernel: [    8.916669] EXT4-fs: delayed allocation enabled
Mar 28 11:49:43 rom-laptop kernel: [    8.916671] EXT4-fs: file extents enabled
Mar 28 11:49:43 rom-laptop kernel: [    8.936599] EXT4-fs: mballoc enabled
Mar 28 11:49:43 rom-laptop kernel: [    8.936602] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 13:04:06 rom-laptop kernel: [ 4473.608227] EXT4-fs: mballoc: 2936 blocks 77 reqs (29 success)
Mar 28 13:04:06 rom-laptop kernel: [ 4473.608231] EXT4-fs: mballoc: 110 extents scanned, 10 goal hits, 40 2^N hits, 0 breaks, 0 lost
Mar 28 13:04:06 rom-laptop kernel: [ 4473.608233] EXT4-fs: mballoc: 2 generated and it took 17255
Mar 28 13:04:06 rom-laptop kernel: [ 4473.608235] EXT4-fs: mballoc: 3634 preallocated, 2604 discarded
Mar 28 13:05:39 rom-laptop kernel: [    3.087459] EXT4-fs: barriers enabled
Mar 28 13:05:39 rom-laptop kernel: [    3.096079] EXT4-fs: delayed allocation enabled
Mar 28 13:05:39 rom-laptop kernel: [    3.096081] EXT4-fs: file extents enabled
Mar 28 13:05:39 rom-laptop kernel: [    3.097601] EXT4-fs: mballoc enabled
Mar 28 13:05:39 rom-laptop kernel: [    3.097605] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 13:05:39 rom-laptop kernel: [    7.940669] EXT4 FS on sda1, internal journal on sda1:8
Mar 28 13:05:39 rom-laptop kernel: [    8.650914] EXT4-fs: barriers enabled
Mar 28 13:05:39 rom-laptop kernel: [    8.651671] EXT4 FS on sda6, internal journal on sda6:8
Mar 28 13:05:39 rom-laptop kernel: [    8.651674] EXT4-fs: delayed allocation enabled
Mar 28 13:05:39 rom-laptop kernel: [    8.651675] EXT4-fs: file extents enabled
Mar 28 13:05:39 rom-laptop kernel: [    8.671616] EXT4-fs: mballoc enabled
Mar 28 13:05:39 rom-laptop kernel: [    8.671619] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 13:11:26 rom-laptop kernel: [    3.131236] EXT4-fs: INFO: recovery required on readonly filesystem.
Mar 28 13:11:26 rom-laptop kernel: [    3.131238] EXT4-fs: write access will be enabled during recovery.
Mar 28 13:11:26 rom-laptop kernel: [    3.161393] EXT4-fs: barriers enabled
Mar 28 13:11:26 rom-laptop kernel: [    3.960680] EXT4-fs: delayed allocation enabled
Mar 28 13:11:26 rom-laptop kernel: [    3.960683] EXT4-fs: file extents enabled
Mar 28 13:11:26 rom-laptop kernel: [    3.962218] EXT4-fs: mballoc enabled
Mar 28 13:11:26 rom-laptop kernel: [    3.962219] EXT4-fs: recovery complete.
Mar 28 13:11:26 rom-laptop kernel: [    3.963079] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 13:11:26 rom-laptop kernel: [    9.358072] EXT4 FS on sda1, internal journal on sda1:8
Mar 28 13:11:26 rom-laptop kernel: [   10.068840] EXT4-fs: barriers enabled
Mar 28 13:11:26 rom-laptop kernel: [   10.069592] EXT4 FS on sda6, internal journal on sda6:8
Mar 28 13:11:26 rom-laptop kernel: [   10.069595] EXT4-fs: delayed allocation enabled
Mar 28 13:11:26 rom-laptop kernel: [   10.069596] EXT4-fs: file extents enabled
Mar 28 13:11:26 rom-laptop kernel: [   10.089565] EXT4-fs: mballoc enabled
Mar 28 13:11:26 rom-laptop kernel: [   10.089568] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 13:20:02 rom-laptop kernel: [  527.094885] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:02 rom-laptop kernel: [  527.160744] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:03 rom-laptop kernel: [  528.447614] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:04 rom-laptop kernel: [  529.163598] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:06 rom-laptop kernel: [  531.164303] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:08 rom-laptop kernel: [  533.165006] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:10 rom-laptop kernel: [  535.165682] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:10 rom-laptop kernel: [  535.166285] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:12 rom-laptop kernel: [  537.167020] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:14 rom-laptop kernel: [  539.167761] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:16 rom-laptop kernel: [  541.168500] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:20:18 rom-laptop kernel: [  543.169148] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:46 rom-laptop kernel: [  631.784316] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:46 rom-laptop kernel: [  631.784973] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:46 rom-laptop kernel: [  631.841672] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:50 rom-laptop kernel: [  635.485618] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:52 rom-laptop kernel: [  637.486347] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:54 rom-laptop kernel: [  639.486982] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:56 rom-laptop kernel: [  641.487624] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:58 rom-laptop kernel: [  643.488279] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:21:58 rom-laptop kernel: [  643.488979] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:00 rom-laptop kernel: [  645.489571] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:02 rom-laptop kernel: [  647.490209] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:04 rom-laptop kernel: [  649.490863] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:06 rom-laptop kernel: [  651.491538] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:06 rom-laptop kernel: [  651.509078] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:08 rom-laptop kernel: [  653.510366] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:10 rom-laptop kernel: [  655.511075] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:12 rom-laptop kernel: [  657.511758] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:14 rom-laptop kernel: [  659.512416] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:14 rom-laptop kernel: [  659.513027] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:16 rom-laptop kernel: [  661.513757] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:18 rom-laptop kernel: [  663.514406] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:20 rom-laptop kernel: [  665.515076] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:22 rom-laptop kernel: [  667.515739] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:27 rom-laptop kernel: [  673.066486] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:27 rom-laptop kernel: [  673.067270] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:27 rom-laptop kernel: [  673.071691] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:29 rom-laptop kernel: [  675.074860] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:31 rom-laptop kernel: [  677.075482] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:33 rom-laptop kernel: [  679.076115] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:35 rom-laptop kernel: [  681.076738] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:35 rom-laptop kernel: [  681.077478] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:35 rom-laptop kernel: [  681.078065] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:38 rom-laptop kernel: [  684.014389] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:41 rom-laptop kernel: [  686.513935] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:42 rom-laptop kernel: [  688.016892] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:44 rom-laptop kernel: [  690.017659] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:46 rom-laptop kernel: [  692.018322] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:47 rom-laptop kernel: [  693.021328] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:47 rom-laptop kernel: [  693.021972] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:47 rom-laptop kernel: [  693.022500] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:48 rom-laptop kernel: [  694.018987] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:49 rom-laptop kernel: [  695.022897] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:50 rom-laptop kernel: [  696.019647] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:50 rom-laptop kernel: [  696.020337] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:51 rom-laptop kernel: [  697.023581] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:52 rom-laptop kernel: [  698.021017] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:53 rom-laptop kernel: [  699.024252] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:54 rom-laptop kernel: [  700.021635] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:55 rom-laptop kernel: [  700.168944] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #412: directory entry across blocks - offset=0, inode=0, rec_len=65536, name_len=0
Mar 28 13:22:55 rom-laptop kernel: [  700.170219] EXT4-fs warning (device sda6): empty_dir: bad directory (dir #412) - no `.' or `..'
Mar 28 13:25:51 rom-laptop kernel: [  876.578492] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=1
Mar 28 13:25:51 rom-laptop kernel: [  876.578995] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=2
Mar 28 13:25:51 rom-laptop kernel: [  876.579449] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=3
Mar 28 13:25:51 rom-laptop kernel: [  876.579640] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=4
Mar 28 13:25:51 rom-laptop kernel: [  876.579826] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=5
Mar 28 13:25:51 rom-laptop kernel: [  876.580043] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=6
Mar 28 13:25:51 rom-laptop kernel: [  876.580235] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=7
Mar 28 13:25:51 rom-laptop kernel: [  876.580422] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=8
Mar 28 13:25:51 rom-laptop kernel: [  876.580607] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=9
Mar 28 13:25:51 rom-laptop kernel: [  876.580794] EXT4-fs error (device sda6): ext4_claim_inode: reserved inode or inode > inodes count - block_group = 0, inode=10
Mar 28 13:26:11 rom-laptop kernel: [  897.082720] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:13 rom-laptop kernel: [  899.083576] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:16 rom-laptop kernel: [  901.084230] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:18 rom-laptop kernel: [  903.084883] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:20 rom-laptop kernel: [  905.085485] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:20 rom-laptop kernel: [  905.086215] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:22 rom-laptop kernel: [  907.086834] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:24 rom-laptop kernel: [  909.087456] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:26 rom-laptop kernel: [  911.088083] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:26:28 rom-laptop kernel: [  913.088769] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:26:28 rom-laptop kernel: [  913.167083] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 516
Mar 28 13:26:28 rom-laptop kernel: [  913.245303] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:07 rom-laptop kernel: [  953.001885] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 314
Mar 28 13:27:08 rom-laptop kernel: [  953.689174] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:08 rom-laptop kernel: [  953.691207] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:08 rom-laptop kernel: [  953.744265] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:08 rom-laptop kernel: [  953.744772] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:09 rom-laptop kernel: [  954.654605] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:09 rom-laptop kernel: [  954.655179] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:13 rom-laptop kernel: [  958.372286] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:15 rom-laptop kernel: [  960.373060] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:17 rom-laptop kernel: [  962.374087] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:19 rom-laptop kernel: [  964.374761] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:21 rom-laptop kernel: [  966.375406] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:21 rom-laptop kernel: [  966.376209] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:23 rom-laptop kernel: [  968.376922] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:25 rom-laptop kernel: [  970.377588] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:27 rom-laptop kernel: [  972.378225] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:29 rom-laptop kernel: [  974.378904] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:29 rom-laptop kernel: [  974.538559] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:31 rom-laptop kernel: [  976.539279] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:33 rom-laptop kernel: [  978.539936] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:35 rom-laptop kernel: [  980.540620] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:27:37 rom-laptop kernel: [  982.541289] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:08 rom-laptop kernel: [ 1013.357318] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 422
Mar 28 13:28:28 rom-laptop kernel: [ 1033.457557] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 524
Mar 28 13:28:28 rom-laptop kernel: [ 1033.565907] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 464
Mar 28 13:28:28 rom-laptop kernel: [ 1033.718509] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:28 rom-laptop kernel: [ 1033.719062] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:28 rom-laptop kernel: [ 1033.719533] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:30 rom-laptop kernel: [ 1035.719881] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:32 rom-laptop kernel: [ 1037.720579] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:34 rom-laptop kernel: [ 1039.721182] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:36 rom-laptop kernel: [ 1041.721854] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:36 rom-laptop kernel: [ 1041.722583] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:36 rom-laptop kernel: [ 1041.723207] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:39 rom-laptop kernel: [ 1044.913749] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 390
Mar 28 13:28:39 rom-laptop kernel: [ 1044.914231] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 391
Mar 28 13:28:39 rom-laptop kernel: [ 1044.914758] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 444
Mar 28 13:28:39 rom-laptop kernel: [ 1044.914992] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 393
Mar 28 13:28:39 rom-laptop kernel: [ 1044.915220] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 527
Mar 28 13:28:39 rom-laptop kernel: [ 1044.915445] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 392
Mar 28 13:28:39 rom-laptop kernel: [ 1044.915659] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 403
Mar 28 13:28:39 rom-laptop kernel: [ 1044.915970] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 402
Mar 28 13:28:39 rom-laptop kernel: [ 1044.916192] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 386
Mar 28 13:28:39 rom-laptop kernel: [ 1044.916537] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 529
Mar 28 13:28:39 rom-laptop kernel: [ 1044.916815] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 476
Mar 28 13:28:39 rom-laptop kernel: [ 1044.917129] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 533
Mar 28 13:28:39 rom-laptop kernel: [ 1044.917340] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 532
Mar 28 13:28:39 rom-laptop kernel: [ 1044.917555] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 531
Mar 28 13:28:39 rom-laptop kernel: [ 1044.917779] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 323
Mar 28 13:28:39 rom-laptop kernel: [ 1044.918012] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 401
Mar 28 13:28:39 rom-laptop kernel: [ 1044.918224] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 387
Mar 28 13:28:39 rom-laptop kernel: [ 1044.918576] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 526
Mar 28 13:28:39 rom-laptop kernel: [ 1044.918789] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 525
Mar 28 13:28:39 rom-laptop kernel: [ 1044.919047] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 388
Mar 28 13:28:39 rom-laptop kernel: [ 1044.919264] EXT4-fs error (device sda6): ext4_free_inode: bit already cleared for inode 389
Mar 28 13:28:45 rom-laptop kernel: [ 1050.986656] EXT4-fs error (device sda6): htree_dirblock_to_tree: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:49 rom-laptop kernel: [ 1054.588208] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:51 rom-laptop kernel: [ 1056.588904] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:53 rom-laptop kernel: [ 1058.589565] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:55 rom-laptop kernel: [ 1060.590193] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:57 rom-laptop kernel: [ 1062.590851] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:57 rom-laptop kernel: [ 1062.591679] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:28:59 rom-laptop kernel: [ 1064.592636] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:01 rom-laptop kernel: [ 1066.593274] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:03 rom-laptop kernel: [ 1068.597092] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:05 rom-laptop kernel: [ 1070.597700] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:05 rom-laptop kernel: [ 1070.748136] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:07 rom-laptop kernel: [ 1072.749068] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:09 rom-laptop kernel: [ 1074.750028] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:11 rom-laptop kernel: [ 1076.750871] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:29:13 rom-laptop kernel: [ 1078.751748] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:38:51 rom-laptop kernel: [ 1656.439047] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:38:53 rom-laptop kernel: [ 1658.442229] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:38:55 rom-laptop kernel: [ 1660.443098] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:38:57 rom-laptop kernel: [ 1662.443913] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:38:59 rom-laptop kernel: [ 1664.444742] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:38:59 rom-laptop kernel: [ 1664.445653] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:39:01 rom-laptop kernel: [ 1666.446455] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:39:03 rom-laptop kernel: [ 1668.447275] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=1764651892, rec_len=25954, name_len=120
Mar 28 13:39:05 rom-laptop kernel: [ 1670.448088] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:39:07 rom-laptop kernel: [ 1672.448927] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:39:07 rom-laptop kernel: [ 1672.591880] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:39:09 rom-laptop kernel: [ 1674.592845] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:39:11 rom-laptop kernel: [ 1676.594062] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:39:13 rom-laptop kernel: [ 1678.594878] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98
Mar 28 13:39:15 rom-laptop kernel: [ 1680.595647] EXT4-fs error (device sda6): ext4_add_entry: bad entry in directory #414: rec_len % 4 != 0 - offset=0, inode=17825816, rec_len=28233, name_len=98

Pourriez-vous essayer la commande chez vous svp?

Et j'ai également de grosses bizarreries : http://forum.ubuntu-fr.org/viewtopic.php?id=304163

nebneo

J'ai pour l'instant pas les messages d'erreur que tu as. Je vais attendre quelques heures et retenter.

[supprimé]

Bonjour,

:-/
Aucune erreur retournée avec :

grep EXT4 /var/log/syslog

A+

nebneo

Après quelques heures, juste une petite erreur, qui ne doit pas être significative, parmi une trentaine de lignes.

®om

Peux-tu poster la ligne en question stp?

beligou_jo

michel2652 a écritAucune erreur retournée avec :

grep EXT4 /var/log/syslog

Bonjour,

Idem pour moi (3 partitions en EXT4 - choix à l'installation) / -- /usr et /home. J'ai laissé /boot en ext3 par prudence, en pensant à grub... ai-je raison ? ou supporte-t-il EXT4 ?

ljere

bonjour,
voici ce que me retourne ta commande ®om je n'ai pas l'impression qu'il y est un souci

ljere@ljere-desktop:~$ grep EXT4 /var/log/syslog
Mar 28 13:58:01 ljere-desktop kernel: [   12.166611] EXT4-fs: barriers enabled
Mar 28 13:58:01 ljere-desktop kernel: [   12.183823] EXT4 FS on sdc1, internal journal on sdc1:8
Mar 28 13:58:01 ljere-desktop kernel: [   12.183827] EXT4-fs: delayed allocation enabled
Mar 28 13:58:01 ljere-desktop kernel: [   12.183829] EXT4-fs: file extents enabled
Mar 28 13:58:01 ljere-desktop kernel: [   12.200420] EXT4-fs: mballoc enabled
Mar 28 13:58:01 ljere-desktop kernel: [   12.200427] EXT4-fs: mounted filesystem with ordered data mode.
Mar 28 15:46:20 ljere-desktop kernel: [   12.122433] EXT4-fs: barriers enabled
Mar 28 15:46:20 ljere-desktop kernel: [   12.139654] EXT4 FS on sdc1, internal journal on sdc1:8
Mar 28 15:46:20 ljere-desktop kernel: [   12.139658] EXT4-fs: delayed allocation enabled
Mar 28 15:46:20 ljere-desktop kernel: [   12.139660] EXT4-fs: file extents enabled
Mar 28 15:46:20 ljere-desktop kernel: [   12.156235] EXT4-fs: mballoc enabled
Mar 28 15:46:20 ljere-desktop kernel: [   12.156243] EXT4-fs: mounted filesystem with ordered data mode.

AlexandreP

beligou_jo a écritJ'ai laissé /boot en ext3 par prudence, en pensant à grub... ai-je raison ? ou supporte-t-il EXT4 ?

From the doc :

Grâce à Curtis Gedak, Ext4 est pris en charge par la nouvelle version de l'éditeur de partitions GParted, et Colin King a apporté la gestion de Ext4 par l'amorceur GRUB. Notez que si vous convertissez votre partition racine ou une partition d'amorçage (/boot) de Ext2 ou Ext3 vers Ext4, vous devrez réinstaller votre amorceur GRUB avec grub-install. Autrement, vous ne serez pas en mesure de démarrer Ubuntu, car la version de GRUB installée dans le secteur d'amorçage de votre disque dur ne reconnaît pas le système de fichiers Ext4 et ne saura donc pas charger un noyau à partir d'une telle partition. Pour une nouvelle installation, GRUB est automatiquement installé avec la gestion de Ext4.

nebneo

®om a écritPeux-tu poster la ligne en question stp?

J'ai reproduit l'erreur ce matin:

[ 9567.720265] EXT4-fs error (device sdd2): ext4_put_super: Couldn't clean up the journal

Mais en fait, c'est parce que j'ai la sale habitude d'éteindre mon dd externe à la bourrin (sans le démonter).

Edit: tant que j'y pense, je cherche précisémment à quoi sert le démontage de volume, si quelqu'un pouvait m'expliquer vite fait l'utilité ce serait sympa 😃 (en quoi démonter est plus propre)

[supprimé]

nebneo a écrit
®om a écritPeux-tu poster la ligne en question stp?
Edit: tant que j'y pense, je cherche précisémment à quoi sert le démontage de volume, si quelqu'un pouvait m'expliquer vite fait l'utilité ce serait sympa 😃 (en quoi démonter est plus propre)

Les écritures ne se font pas directement sur le disque, on passe d'abord par des blocs, qui une fois pleins, sont écrit physiquement sur le disque dur. Si tu éteints ton disque dur alors que les informations se trouvant dans les blocs n'ont pas été écrites sur ton hdd, alors tu auras des problèmes ;-)

beligou_jo

AlexandreP a écrit
beligou_jo a écritJ'ai laissé /boot en ext3 par prudence, en pensant à grub... ai-je raison ? ou supporte-t-il EXT4 ?
From the doc :

Merci pour la documentation, je savais que j'avais vu quelque chose à ce sujet, mais où ?

Je viens de télécharger GPARTED à jour de EXT4. N'ayant pas de données sur cette version je réinstallerai Jaunty proprement en EXT4 lors de la sortie de la version finale. 🙂

®om

Bon, eh bien ça vient de mon disque dur : j'ai tout formaté en EXT3, j'ai toujours plein de problèmes…
http://forum.ubuntu-fr.org/viewtopic.php?id=304880

®om

Bon en fait j'ai parlé un peu trop vite, ça plante en EXT3 et EXT4 sous Jaunty (depuis une mise à jour à partir de l'alpha 4), mais j'ai réinstallé intrepid, ça fonctionne !

Ce n'est donc pas un problème matériel.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/350268

Blackpegaz

Je confirme, je suis dans le même cas que toi.

Hoxus

Bonjour,

Désolé, je déterre un topic pas mal agé, mais je suis dans le même cas.

Je travaille avec un Dell precision 390, sur lequel j'ai installé Karmic (9.10), version 32 bits, en dual boot avec windows.

J'ai fait une install fraîche en ext4 il y a quelques mois.
Il me semble que ça a bien fonctionné quelques jours (j'ai peut être simplement eu de la chance), mais depuis je perds régulièrement les droits d'écritures sur mon /home.

Parfois au bout d'une demi heure, parfois après 48h...
J'ai tenté de désinstaller une appli (boinc, qui fait du calcul partagé), de remettre le fstab d'origine (je l'avais modifié pour monter Windows), mais rien de changé.
Ca arrive n'importe quand, et je ne vois pas d'application que je lance et qui pourrait être responsable de ça.

J'ai cherché (la preuve, je suis tombé sur ce post :cool:), mais je n'ai rien trouvé de satisfaisant.
Avez-vous une idée, ou un tuyaux ?

Merci d'avance,
Hoxus