/dev/dm-12 und dm-13 device error

[swoop]

Hallo Leute,

ich brauch bitte ganz dringend Eure Hilfe.
vor etwas über einem Jahr habe ich ein Server installiert, der bis jetzt tadellos funktioniert hal. Jetzt macht er aber Mucken und startet teilweise die VMs bzw. LXCs nicht meht.
Vermutich ist die SSD das problem, denn ich hab folgende Meldungen per DMESG gesehen.

[ 9727.504675] EXT4-fs error (device dm-12): ext4_find_extent:924: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.505716] EXT4-fs error (device dm-12): ext4_ext_remove_space:2984: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.506849] EXT4-fs error (device dm-12): ext4_find_extent:924: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.508026] EXT4-fs error (device dm-12): ext4_find_extent:924: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.509270] EXT4-fs error (device dm-12): ext4_ext_remove_space:2984: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.510625] EXT4-fs error (device dm-12): ext4_find_extent:924: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.511990] EXT4-fs error (device dm-12): ext4_find_extent:924: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.513353] EXT4-fs error (device dm-12): ext4_ext_remove_space:2984: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9727.514749] EXT4-fs error (device dm-12): ext4_find_extent:924: inode #264401: comm database: pblk 1081510 bad header/extent: extent tree corrupted - magic f30a, entries 17, max 340(340), depth 0(0)
[ 9728.995841] EXT4-fs warning (device dm-12): ext4_end_bio:342: I/O error 3 writing to inode 132316 starting block 1105427)
[ 9728.995852] Buffer I/O error on device dm-12, logical block 1105427
[ 9729.000493] EXT4-fs warning (device dm-12): ext4_end_bio:342: I/O error 3 writing to inode 132331 starting block 1105428)
[ 9734.002355] EXT4-fs warning (device dm-12): ext4_end_bio:342: I/O error 3 writing to inode 132316 starting block 1105427)
[ 9734.002359] buffer_io_error: 1 callbacks suppressed
[ 9734.002359] Buffer I/O error on device dm-12, logical block 1105427
[ 9734.003027] EXT4-fs warning (device dm-12): ext4_end_bio:342: I/O error 3 writing to inode 132331 starting block 1105428)
[ 9734.003029] Buffer I/O error on device dm-12, logical block 1105428

wie find ich jetzt raus welches device dm-12 ist?

SG

 

[swoop]

Hallo,

das unmittelbare Problem, das ich habe, scheint vorerst behoben.
Allerdings interssiert es mich trotzdem.
Wohin wird das zB dm-1 gemappt bzw. wo liegen die DM-x, die das Log bemängelt?

SG

 

[swoop]

hallo,

keiner ne Idee?

SG