#176 Le 21/03/2023, à 17:31
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Une bonne nouvelle en soit. Dans la trace, je vois que tout est bien mis en route. A mon avis, il va maintenant commencer le remplacement de SDC3 par SDB3.
Feb 28 16:24:13 vhs-4 kernel: [ 9.891367] md/raid1:md0: active with 4 out of 4 mirrors
Feb 28 16:24:13 vhs-4 kernel: [ 9.891400] md0: detected capacity change from 0 to 5000593408
Feb 28 16:24:13 vhs-4 kernel: [ 9.892341] md0: unknown partition table
Feb 28 16:24:13 vhs-4 kernel: [ 10.073377] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Feb 28 16:24:13 vhs-4 kernel: [ 10.073639] EXT4-fs (md0): couldn't mount as ext2 due to feature incompatibilities
Feb 28 16:24:13 vhs-4 kernel: [ 10.841991] EXT4-fs (md0): recovery complete
Feb 28 16:24:13 vhs-4 kernel: [ 10.867338] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Feb 28 16:24:13 vhs-4 kernel: [ 15.936171] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Feb 28 16:24:13 vhs-4 kernel: [ 18.431123] EXT4-fs (md0): re-mounted. Opts: (null)Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#177 Le 21/03/2023, à 17:34
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Je me fais souvent avoir dans les frappes
journalctl --no-pager -b -g sdajournalctl --no-pager -b -g "GPT:Primary "Dernière modification par geole (Le 21/03/2023, à 18:12)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#178 Le 21/03/2023, à 17:40
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
jm@jm-OptiPlex-9020:~$ journalctl --no-pager -b -g sda
-- Logs begin at Fri 2023-03-10 22:01:39 CET, end at Tue 2023-03-21 16:40:28 CET. --
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sd 0:0:0:0: [sda] Write Protect is off
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sda: sda1 sda2 sda3
mars 21 09:52:46 jm-OptiPlex-9020 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
mars 21 09:52:56 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda, type changed from 'scsi' to 'sat'
mars 21 09:52:56 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], opened
mars 21 09:52:56 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], WDC WD30EFAX-68JH4N1, S/N:WD-WX52D312ZXFA, WWN:5-0014ee-21427eac9, FW:83.00A83, 3.00 TB
mars 21 09:52:56 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], not found in smartd database.
mars 21 09:52:56 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
mars 21 09:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.WDC_WD30EFAX_68JH4N1-WD_WX52D312ZXFA.ata.state
mars 21 09:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 126 to 123
mars 21 09:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD30EFAX_68JH4N1-WD_WX52D312ZXFA.ata.state
mars 21 10:12:53 jm-OptiPlex-9020 sudo[2879]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md127 /dev/sda2 /dev/sdd2
mars 21 10:12:53 jm-OptiPlex-9020 kernel: md: kicking non-fresh sda2 from array!
mars 21 10:14:47 jm-OptiPlex-9020 sudo[2939]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdc3/dev/sdd3
mars 21 10:21:32 jm-OptiPlex-9020 sudo[2977]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run --update=resync /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
mars 21 10:22:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 123 to 122
mars 21 10:33:32 jm-OptiPlex-9020 sudo[3097]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
mars 21 10:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 121
mars 21 11:00:00 jm-OptiPlex-9020 sudo[3361]: jm : TTY=pts/1 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --manage /dev/md127 --add /dev/sda2
mars 21 11:08:32 jm-OptiPlex-9020 sudo[3513]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdd3
mars 21 11:08:32 jm-OptiPlex-9020 kernel: md/raid:md3: device sda3 operational as raid disk 0
mars 21 11:10:46 jm-OptiPlex-9020 sudo[3593]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
mars 21 11:19:58 jm-OptiPlex-9020 sudo[3668]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
mars 21 11:22:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 121 to 120
mars 21 11:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 120 to 121
mars 21 12:22:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 121 to 122
mars 21 13:15:35 jm-OptiPlex-9020 sudo[3977]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdd3
mars 21 13:16:24 jm-OptiPlex-9020 sudo[3982]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdd3
mars 21 13:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 122 to 121
mars 21 15:52:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 121 to 120
mars 21 16:22:57 jm-OptiPlex-9020 smartd[944]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 120 to 119Hors ligne
#179 Le 21/03/2023, à 17:57
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Encore plus surprenant
A ce niveau, il y a les disques au démarrage et il se stoppe sans que je vois un message explicatif
J'ai juste vu:
Feb 28 19:09:16 vhs-4 kernel: [ 1.154336] GPT:Primary header thinks Alt. header is not at the end of the disk.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154338] GPT:1565565871 != 5860533167
Feb 28 19:09:16 vhs-4 kernel: [ 1.154339] GPT:Alternate GPT header not at the end of the disk.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154340] GPT:1565565871 != 5860533167
Feb 28 19:09:16 vhs-4 kernel: [ 1.154341] GPT: Use GNU Parted to correct GPT errors.
Mais il ne semble pas dire que c'est grave.
Feb 28 19:09:16 vhs-4 kernel: [ 1.117043] sd 0:0:0:0: [sda] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 28 19:09:16 vhs-4 kernel: [ 1.117046] sd 0:0:0:0: [sda] 4096-byte physical blocks
Feb 28 19:09:16 vhs-4 kernel: [ 1.117050] sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 28 19:09:16 vhs-4 kernel: [ 1.117094] sd 0:0:0:0: [sda] Write Protect is off
Feb 28 19:09:16 vhs-4 kernel: [ 1.117096] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 28 19:09:16 vhs-4 kernel: [ 1.117112] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 28 19:09:16 vhs-4 kernel: [ 1.117229] scsi 1:0:0:0: Direct-Access ATA WDC WD30EFRX-68A 0A80 PQ: 0 ANSI: 5
Feb 28 19:09:16 vhs-4 kernel: [ 1.117376] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 28 19:09:16 vhs-4 kernel: [ 1.117380] sd 1:0:0:0: [sdb] 4096-byte physical blocks
Feb 28 19:09:16 vhs-4 kernel: [ 1.117408] sd 1:0:0:0: Attached scsi generic sg1 type 0
Feb 28 19:09:16 vhs-4 kernel: [ 1.117459] sd 1:0:0:0: [sdb] Write Protect is off
Feb 28 19:09:16 vhs-4 kernel: [ 1.117462] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Feb 28 19:09:16 vhs-4 kernel: [ 1.117496] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 28 19:09:16 vhs-4 kernel: [ 1.117532] scsi 4:0:0:0: Direct-Access ATA WDC WD30EFRX-68A 0A80 PQ: 0 ANSI: 5
Feb 28 19:09:16 vhs-4 kernel: [ 1.117689] sd 4:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 28 19:09:16 vhs-4 kernel: [ 1.117691] sd 4:0:0:0: [sdc] 4096-byte physical blocks
Feb 28 19:09:16 vhs-4 kernel: [ 1.117759] sd 4:0:0:0: [sdc] Write Protect is off
Feb 28 19:09:16 vhs-4 kernel: [ 1.117762] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Feb 28 19:09:16 vhs-4 kernel: [ 1.117790] sd 4:0:0:0: Attached scsi generic sg2 type 0
Feb 28 19:09:16 vhs-4 kernel: [ 1.117793] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 28 19:09:16 vhs-4 kernel: [ 1.117887] scsi 5:0:0:0: Direct-Access ATA WDC WD30EFRX-68A 0A80 PQ: 0 ANSI: 5
Feb 28 19:09:16 vhs-4 kernel: [ 1.118041] sd 5:0:0:0: [sdd] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 28 19:09:16 vhs-4 kernel: [ 1.118043] sd 5:0:0:0: [sdd] 4096-byte physical blocks
Feb 28 19:09:16 vhs-4 kernel: [ 1.118063] sd 5:0:0:0: Attached scsi generic sg3 type 0
Feb 28 19:09:16 vhs-4 kernel: [ 1.118115] sd 5:0:0:0: [sdd] Write Protect is off
Feb 28 19:09:16 vhs-4 kernel: [ 1.118117] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Feb 28 19:09:16 vhs-4 kernel: [ 1.118151] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 28 19:09:16 vhs-4 kernel: [ 1.130718] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
Feb 28 19:09:16 vhs-4 kernel: [ 1.130721] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 28 19:09:16 vhs-4 kernel: [ 1.131005] hub 1-1:1.0: USB hub found
Feb 28 19:09:16 vhs-4 kernel: [ 1.131092] hub 1-1:1.0: 4 ports detected
Feb 28 19:09:16 vhs-4 kernel: [ 1.154336] GPT:Primary header thinks Alt. header is not at the end of the disk.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154338] GPT:1565565871 != 5860533167
Feb 28 19:09:16 vhs-4 kernel: [ 1.154339] GPT:Alternate GPT header not at the end of the disk.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154340] GPT:1565565871 != 5860533167
Feb 28 19:09:16 vhs-4 kernel: [ 1.154341] GPT: Use GNU Parted to correct GPT errors.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154348] sdb: sdb1 sdb2 sdb3
Feb 28 19:09:16 vhs-4 kernel: [ 1.154956] sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 28 19:09:16 vhs-4 kernel: [ 1.171446] sdc: sdc1 sdc2 sdc3
Feb 28 19:09:16 vhs-4 kernel: [ 1.172289] sd 4:0:0:0: [sdc] Attached SCSI disk
Feb 28 19:09:16 vhs-4 kernel: [ 1.172812] sda: sda1 sda2 sda3
Feb 28 19:09:16 vhs-4 kernel: [ 1.173234] sd 0:0:0:0: [sda] Attached SCSI disk
Feb 28 19:09:16 vhs-4 kernel: [ 1.176992] sdd: sdd1 sdd2 sdd3
Feb 28 19:09:16 vhs-4 kernel: [ 1.177645] sd 5:0:0:0: [sdd] Attached SCSI disk
Feb 28 19:09:16 vhs-4 kernel: [ 1.242676] usb 2-1: new high-speed USB device number 2 using ehci-pci
Feb 28 19:09:16 vhs-4 kernel: [ 1.305063] hidraw: raw HID events driver (C) Jiri Kosina
Feb 28 19:09:16 vhs-4 kernel: [ 1.375151] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
Feb 28 19:09:16 vhs-4 kernel: [ 1.375154] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 28 19:09:16 vhs-4 kernel: [ 1.375464] hub 2-1:1.0: USB hub found
Feb 28 19:09:16 vhs-4 kernel: [ 1.375647] hub 2-1:1.0: 6 ports detected
Feb 28 19:09:16 vhs-4 kernel: [ 1.387149] md: linear personality registered for level -1
Feb 28 19:09:16 vhs-4 kernel: [ 1.389196] md: multipath personality registered for level -4
Feb 28 19:09:16 vhs-4 kernel: [ 1.391328] md: raid0 personality registered for level 0
Feb 28 19:09:16 vhs-4 kernel: [ 1.393843] md: raid1 personality registered for level 1
Feb 28 19:09:16 vhs-4 kernel: [ 1.446847] usb 1-1.1: new high-speed USB device number 3 using ehci-pci
Feb 28 19:09:16 vhs-4 kernel: [ 1.462802] raid6: sse2x1 8528 MB/s
Feb 28 19:09:16 vhs-4 kernel: [ 1.530878] raid6: sse2x2 10503 MB/s
Feb 28 19:09:16 vhs-4 kernel: [ 1.542487] usb 1-1.1: New USB device found, idVendor=0951, idProduct=1665
Feb 28 19:09:16 vhs-4 kernel: [ 1.542490] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 28 19:09:16 vhs-4 kernel: [ 1.542499] usb 1-1.1: Product: DataTraveler 2.0
Feb 28 19:09:16 vhs-4 kernel: [ 1.542500] usb 1-1.1: Manufacturer: Kingston
Feb 28 19:09:16 vhs-4 kernel: [ 1.542501] usb 1-1.1: SerialNumber: 50E549C20268BD408981133B
Feb 28 19:09:16 vhs-4 kernel: [ 1.545510] usb-storage 1-1.1:1.0: USB Mass Storage device detected
Feb 28 19:09:16 vhs-4 kernel: [ 1.545666] scsi6 : usb-storage 1-1.1:1.0
Feb 28 19:09:16 vhs-4 kernel: [ 1.545738] usbcore: registered new interface driver usb-storage
Feb 28 19:09:16 vhs-4 kernel: [ 1.546972] usbcore: registered new interface driver uas
Feb 28 19:09:16 vhs-4 kernel: [ 1.598957] raid6: sse2x4 11560 MB/s
Feb 28 19:09:16 vhs-4 kernel: [ 1.598959] raid6: using algorithm sse2x4 (11560 MB/s)
Feb 28 19:09:16 vhs-4 kernel: [ 1.598960] raid6: using ssse3x2 recovery algorithm
Feb 28 19:09:16 vhs-4 kernel: [ 1.599944] xor: automatically using best checksumming function:
Feb 28 19:09:16 vhs-4 kernel: [ 1.615067] usb 1-1.2: new low-speed USB device number 4 using ehci-pci
Feb 28 19:09:16 vhs-4 kernel: [ 1.638997] avx : 24132.000 MB/sec
Feb 28 19:09:16 vhs-4 kernel: [ 1.639035] tsc: Refined TSC clocksource calibration: 2494.334 MHz
Feb 28 19:09:16 vhs-4 kernel: [ 1.639911] async_tx: api initialized (async)
Feb 28 19:09:16 vhs-4 kernel: [ 1.646463] md: raid6 personality registered for level 6
Feb 28 19:09:16 vhs-4 kernel: [ 1.646465] md: raid5 personality registered for level 5
Feb 28 19:09:16 vhs-4 kernel: [ 1.646466] md: raid4 personality registered for level 4
Feb 28 19:09:16 vhs-4 kernel: [ 1.651351] md: raid10 personality registered for level 10
Feb 28 19:09:16 vhs-4 kernel: [ 1.713928] usb 1-1.2: New USB device found, idVendor=0fc5, idProduct=b080
Feb 28 19:09:16 vhs-4 kernel: [ 1.713930] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 28 19:09:16 vhs-4 kernel: [ 1.713932] usb 1-1.2: Product: USB IO Controller
Feb 28 19:09:16 vhs-4 kernel: [ 1.713933] usb 1-1.2: Manufacturer: Delcom Products Inc.
Feb 28 19:09:16 vhs-4 kernel: [ 1.721571] usbcore: registered new interface driver usbhid
Feb 28 19:09:16 vhs-4 kernel: [ 1.721573] usbhid: USB HID core driver
Feb 28 19:09:16 vhs-4 kernel: [ 1.736259] hid-generic 0003:0FC5:B080.0001: hiddev0,hidraw0: USB HID v1.00 Device [Delcom Products Inc. USB IO Controller ] on usb-0000:00:1a.0-1.2/input0
Feb 28 19:09:16 vhs-4 kernel: [ 2.546366] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4
Feb 28 19:09:16 vhs-4 kernel: [ 2.546658] sd 6:0:0:0: Attached scsi generic sg4 type 0
Feb 28 19:09:16 vhs-4 kernel: [ 2.547486] sd 6:0:0:0: [sde] 15356160 512-byte logical blocks: (7.86 GB/7.32 GiB)
Feb 28 19:09:16 vhs-4 kernel: [ 2.548391] sd 6:0:0:0: [sde] Write Protect is off
Feb 28 19:09:16 vhs-4 kernel: [ 2.548394] sd 6:0:0:0: [sde] Mode Sense: 23 00 00 00
Feb 28 19:09:16 vhs-4 kernel: [ 2.549176] sd 6:0:0:0: [sde] No Caching mode page found
Feb 28 19:09:16 vhs-4 kernel: [ 2.549189] sd 6:0:0:0: [sde] Assuming drive cache: write through
Feb 28 19:09:16 vhs-4 kernel: [ 2.554062] sde: sde1
Feb 28 19:09:16 vhs-4 kernel: [ 2.557309] sd 6:0:0:0: [sde] Attached SCSI removable disk
Feb 28 19:09:16 vhs-4 kernel: [ 2.640273] Switched to clocksource tsc
Feb 28 19:09:16 vhs-4 kernel: [ 2.824827] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Feb 28 19:09:16 vhs-4 kernel: [ 6.663700] random: nonblocking pool is initialized
Feb 28 19:09:16 vhs-4 kernel: [ 7.075195] md: md0 stopped.Dernière modification par geole (Le 21/03/2023, à 22:49)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#180 Le 21/03/2023, à 18:11
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
journalctl --no-pager -b -g "GPT:Primary "Je crains que le message "GPT:Primary" soit la cause du blocage. Avais-tu fait la correction?
Dernière modification par geole (Le 21/03/2023, à 18:22)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#181 Le 21/03/2023, à 18:14
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Geole a écrit :
J ai vu que le message "GPT:Primary" soit la cause du blogace
Avais-tu fait la correction?
Si oui, il est quasiment certain qu il faut rebooter pour prise en compte de la rectification Je ne l avais pas précisé
Je comprends pas trop ta question, je dois corriger quoi ?
jm@jm-OptiPlex-9020:~$ journalctl --no-pager -b -g "GPT:Primary "
-- Logs begin at Fri 2023-03-10 22:01:39 CET, end at Tue 2023-03-21 17:18:52 CET. --
-- No entries --Dernière modification par Jm78 (Le 21/03/2023, à 18:19)
Hors ligne
#182 Le 21/03/2023, à 18:23
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Je dis une connerie, il me semble que j'avais vérifié que le disque double n'a pas cette erreur.
Dernière modification par geole (Le 21/03/2023, à 22:48)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#183 Le 21/03/2023, à 18:30
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Geole a écrit :
Tu lances gparted,,
Ok, mais quand je clique sur Périphériques, j'ai pas supprimer la table de partition :
j'ai "Créer une table..."ou "Tenter récupération de donnes"
Est-ce qu'il faut se mettre sur un disque en particulier avant de cliquer sur Péripheriques ?
Hors ligne
#184 Le 21/03/2023, à 18:36
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Oublie gparted
et donne
sudo fdisk -l /dev/sdbSinon, il faut d'abord choisir le disque.
Jm78 a écrit :
jm@jm-OptiPlex-9020:~$ journalctl --no-pager -b -g sda -- Logs begin at Fri 2023-03-10 22:01:39 CET, end at Tue 2023-03-21 16:40:28 CET. -- mars 21 10:14:47 jm-OptiPlex-9020 sudo[2939]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdc3/dev/sdd3 mars 21 10:21:32 jm-OptiPlex-9020 sudo[2977]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run --update=resync /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 mars 21 10:33:32 jm-OptiPlex-9020 sudo[3097]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 mars 21 11:08:32 jm-OptiPlex-9020 sudo[3513]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdb3 /dev/sdd3 mars 21 11:08:32 jm-OptiPlex-9020 kernel: md/raid:md3: device sda3 operational as raid disk 0 mars 21 11:19:58 jm-OptiPlex-9020 sudo[3668]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 mars 21 13:15:35 jm-OptiPlex-9020 sudo[3977]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdd3 mars 21 13:16:24 jm-OptiPlex-9020 sudo[3982]: jm : TTY=pts/0 ; PWD=/home/jm ; USER=root ; COMMAND=/usr/sbin/mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdd3
Je n'ai conservé que nos commandes.
Donc, je te propose de rebooter et de tenter cette commande
sudo mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdd3On voit que SDA a été activé une fois et une seule par nos commandes.
Dernière modification par geole (Le 21/03/2023, à 22:47)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#185 Le 21/03/2023, à 18:50
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
jm@jm-OptiPlex-9020:~$ sudo fdisk -l /dev/sdb
[sudo] Mot de passe de jm :
Disque /dev/sdb : 2,75 TiB, 3000592982016 octets, 5860533168 secteurs
Disk model: WDC WD30EFAX-68J
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets
Type d'étiquette de disque : gpt
Identifiant de disque : E8E6D426-7206-4B9C-A98B-D5C4A697722D
Périphérique Début Fin Secteurs Taille Type
/dev/sdb1 40 996095 996056 486,4M RAID Linux
/dev/sdb2 996096 10763671 9767576 4,7G Système EFI
/dev/sdb3 10763672 5860533134 5849769463 2,7T RAID LinuxHors ligne
#186 Le 21/03/2023, à 18:58
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Je viens de Rebooter
MD3 est revenu
jm@jm-OptiPlex-9020:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active raid1 sdd2[4] sda2[2]
4883392 blocks super 1.0 [2/2] [UU]
md3 : inactive sda3[0](S) sdd3[4](S) sdb3[5](S) sdc3[2](S)
11699537608 blocks super 1.0
unused devices: <none>jm@jm-OptiPlex-9020:~$ sudo mdadm --assemble --verbose --metadata=1.0 --force --run /dev/md3 /dev/sda3 /dev/sdd3
mdadm: looking for devices for /dev/md3
mdadm: /dev/sda3 is busy - skipping
mdadm: /dev/sdd3 is busy - skippingHors ligne
#187 Le 21/03/2023, à 19:10
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Je voulais dire que le message que tu avais signalé dans la commande fdisk était visible dans la trace de 19 heures..... sous cette forme
Feb 28 19:09:16 vhs-4 kernel: [ 1.154336] GPT:Primary header thinks Alt. header is not at the end of the disk.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154338] GPT:1565565871 != 5860533167
Feb 28 19:09:16 vhs-4 kernel: [ 1.154339] GPT:Alternate GPT header not at the end of the disk.
Feb 28 19:09:16 vhs-4 kernel: [ 1.154340] GPT:1565565871 != 5860533167
Feb 28 19:09:16 vhs-4 kernel: [ 1.154341] GPT: Use GNU Parted to correct GPT errorsMais il ne l'était pas avant. Je suis donc en train de supposer que ' c est la cause du recovery qui se plante...
Je rêve un peu...
Le disque initial est composé de la façon suivante:
La table primaire GPT de 34 secteurs.
La première partition.
La seconde partition.
1 To de la troisième partition.
La table de sécurité GPT de 34 secteurs.
2 To de la troisième partition.
Pour une raison que je ne saurais retrouver, cette table de sécurité est venue se mettre à cet endroit (donc au 1/3 de la troisième partition) après la création de la partition faite en 2013. Cette erreur a donc pu se faire dans une période de 10 ans
Maintenant, à cause du disque SDC défaillant, on a besoin du disque SDB.
La copie de SDC3 sur SDB3 commence et bute systématiquement sur ce double de table de partition ( Souviens-toi du message) qu'elle ne sait pas franchir.
Dernière modification par geole (Le 21/03/2023, à 22:45)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#188 Le 21/03/2023, à 19:17
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Si ta réflexion est bonne, ca veut dire que mes données sont perdues ?
Hors ligne
#189 Le 21/03/2023, à 19:21
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Tu me laisses encore combien de temps pour chercher une cause au busy?
Sinon, c'est la fin du paragraphe 6.1
J'ai ajouté très récemment ces mots "Si les données ne sont pas dégradées, elles sont retrouvées. " ainsi que la commande
Je tiens à préciser que si on fait une petite erreur, on peut ne retrouver que les noms de fichiers sans les données ou rien . Mais tu as un double. Malheureusement mon essai était en version 1.20 et pas 1.0
Dernière modification par geole (Le 21/03/2023, à 22:44)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#190 Le 21/03/2023, à 19:25
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Je te laisse tout le temps que tu veux... c'est déjà génial que tu m'accordes autant de ton temps !
Hors ligne
#191 Le 21/03/2023, à 19:34
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Un peu de présentation très très rapide du fonctionnement RAID5 ou plutôt RAID4 dans cette description
Disque A contient les paquets pairs des données.
Disque B contient les paquets impairs des données.
Disque C contient La parité des deux paquets.
Disque D est un disque SPARE
Un des disques vient de lâcher
On va donc activer le disque de secours et reconstruire le disque H.S. aà partir des deux disques sains.
C est possible grâce à l utilisation de la parité.
exemple
0 0 0
0 1 1
1 0 1
1 1 0
Supprime une colonne, imagine ce que tu dois remettre pour être en concordance avec les deux autres colonnes.
A chaque fois, il n y a qu un seul choix
Je reste convaincu qu on est bloqué dans cette étape de reconstitution.
Dernière modification par geole (Le 21/03/2023, à 19:35)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#192 Le 21/03/2023, à 19:49
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Merci pour le temps accordé
Encore un petit de tail pour connaitre la cause initiale. J'aurais peut-être mieux fait de commencer par le début....
tail -7000 /mnt/var/log/syslog.1 | head -1000Dernière modification par geole (Le 21/03/2023, à 22:43)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#193 Le 21/03/2023, à 19:55
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Merci pour tes explications,
Lorsque le serveur m'a signalé un problème,
je me suis connecté au serveur et j'ai découvert que le SDC était Hors Service, et les 3 autres disques étaient opérationnels
j'avais accès a mes données donc ca veut dire que la reconstruction avait été faites ?
Et c'est quand l'application du serveur m'a proposé de "Réparer" le problème sur le SDC (qui s'est mal terminée ) que j'ai perdu le SDB après le reboot
Je comprends pas pourquoi l'application de configuration du serveur m'a proposé de "réparer" le problème vu que c'était les même disks en place !!!
Quel problème aurait-il pu réparer si c'était le disk SDC qui était HS ? Et pourquoi le disk SDB s'est retrouvé exclu du RAID ?
Et quand on n'y connait rien, on se rend pas compte des conséquences de nos actions !!!
Hors ligne
#194 Le 21/03/2023, à 20:00
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
jm@jm-OptiPlex-9020:~$ tail -10000 /mnt/var/log/syslog.1 | head -1000
Feb 28 15:23:21 vhs-4 kernel: [ 138.841369] ata2.00: exception Emask 0x0 SAct 0x40000000 SErr 0x0 action 0x0
Feb 28 15:23:21 vhs-4 kernel: [ 138.841375] ata2.00: irq_stat 0x40000008
Feb 28 15:23:21 vhs-4 kernel: [ 138.841379] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:23:21 vhs-4 kernel: [ 138.841386] ata2.00: cmd 60/08:f0:f0:3f:a4/00:00:00:00:00/40 tag 30 ncq 4096 in
Feb 28 15:23:21 vhs-4 kernel: [ 138.841386] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:23:21 vhs-4 kernel: [ 138.841389] ata2.00: status: { DRDY ERR }
Feb 28 15:23:21 vhs-4 kernel: [ 138.841391] ata2.00: error: { UNC }
Feb 28 15:23:21 vhs-4 kernel: [ 138.842855] ata2.00: configured for UDMA/133
Feb 28 15:23:21 vhs-4 kernel: [ 138.842867] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:23:21 vhs-4 kernel: [ 138.842869] sd 1:0:0:0: [sdb]
Feb 28 15:23:21 vhs-4 kernel: [ 138.842871] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:23:21 vhs-4 kernel: [ 138.842873] sd 1:0:0:0: [sdb]
Feb 28 15:23:21 vhs-4 kernel: [ 138.842875] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:23:21 vhs-4 kernel: [ 138.842879] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:23:21 vhs-4 kernel: [ 138.842880] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:23:21 vhs-4 kernel: [ 138.842889] 00 a4 3f f1
Feb 28 15:23:21 vhs-4 kernel: [ 138.842894] sd 1:0:0:0: [sdb]
Feb 28 15:23:21 vhs-4 kernel: [ 138.842896] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:23:21 vhs-4 kernel: [ 138.842898] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:23:21 vhs-4 kernel: [ 138.842900] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:23:21 vhs-4 kernel: [ 138.842911] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:23:21 vhs-4 kernel: [ 138.842924] ata2: EH complete
Feb 28 15:23:42 vhs-4 kernel: [ 159.698746] ata2.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
Feb 28 15:23:42 vhs-4 kernel: [ 159.698751] ata2.00: irq_stat 0x40000008
Feb 28 15:23:42 vhs-4 kernel: [ 159.698755] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:23:42 vhs-4 kernel: [ 159.698762] ata2.00: cmd 60/08:80:f0:3f:a4/00:00:00:00:00/40 tag 16 ncq 4096 in
Feb 28 15:23:42 vhs-4 kernel: [ 159.698762] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:23:42 vhs-4 kernel: [ 159.698765] ata2.00: status: { DRDY ERR }
Feb 28 15:23:42 vhs-4 kernel: [ 159.698767] ata2.00: error: { UNC }
Feb 28 15:23:42 vhs-4 kernel: [ 159.700770] ata2.00: configured for UDMA/133
Feb 28 15:23:42 vhs-4 kernel: [ 159.700780] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:23:42 vhs-4 kernel: [ 159.700783] sd 1:0:0:0: [sdb]
Feb 28 15:23:42 vhs-4 kernel: [ 159.700785] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:23:42 vhs-4 kernel: [ 159.700787] sd 1:0:0:0: [sdb]
Feb 28 15:23:42 vhs-4 kernel: [ 159.700789] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:23:42 vhs-4 kernel: [ 159.700799] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:23:42 vhs-4 kernel: [ 159.700800] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:23:42 vhs-4 kernel: [ 159.700805] 00 a4 3f f1
Feb 28 15:23:42 vhs-4 kernel: [ 159.700808] sd 1:0:0:0: [sdb]
Feb 28 15:23:42 vhs-4 kernel: [ 159.700810] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:23:42 vhs-4 kernel: [ 159.700811] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:23:42 vhs-4 kernel: [ 159.700812] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:23:42 vhs-4 kernel: [ 159.700818] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:23:42 vhs-4 kernel: [ 159.700826] ata2: EH complete
Feb 28 15:23:49 vhs-4 kernel: [ 167.195471] ata2.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x0
Feb 28 15:23:49 vhs-4 kernel: [ 167.195477] ata2.00: irq_stat 0x40000008
Feb 28 15:23:49 vhs-4 kernel: [ 167.195481] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:23:49 vhs-4 kernel: [ 167.195488] ata2.00: cmd 60/08:c8:f0:3f:a4/00:00:00:00:00/40 tag 25 ncq 4096 in
Feb 28 15:23:49 vhs-4 kernel: [ 167.195488] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:23:49 vhs-4 kernel: [ 167.195491] ata2.00: status: { DRDY ERR }
Feb 28 15:23:49 vhs-4 kernel: [ 167.195493] ata2.00: error: { UNC }
Feb 28 15:23:49 vhs-4 kernel: [ 167.196554] ata2.00: configured for UDMA/133
Feb 28 15:23:49 vhs-4 kernel: [ 167.196566] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:23:49 vhs-4 kernel: [ 167.196569] sd 1:0:0:0: [sdb]
Feb 28 15:23:49 vhs-4 kernel: [ 167.196571] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:23:49 vhs-4 kernel: [ 167.196573] sd 1:0:0:0: [sdb]
Feb 28 15:23:49 vhs-4 kernel: [ 167.196575] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:23:49 vhs-4 kernel: [ 167.196579] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:23:49 vhs-4 kernel: [ 167.196580] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:23:49 vhs-4 kernel: [ 167.196589] 00 a4 3f f1
Feb 28 15:23:49 vhs-4 kernel: [ 167.196594] sd 1:0:0:0: [sdb]
Feb 28 15:23:49 vhs-4 kernel: [ 167.196596] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:23:49 vhs-4 kernel: [ 167.196599] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:23:49 vhs-4 kernel: [ 167.196600] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:23:49 vhs-4 kernel: [ 167.196611] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:23:49 vhs-4 kernel: [ 167.196622] ata2: EH complete
Feb 28 15:24:01 vhs-4 CRON[10946]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:24:12 vhs-4 kernel: [ 190.098149] ata2.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
Feb 28 15:24:12 vhs-4 kernel: [ 190.098152] ata2.00: irq_stat 0x40000008
Feb 28 15:24:12 vhs-4 kernel: [ 190.098154] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:24:12 vhs-4 kernel: [ 190.098158] ata2.00: cmd 60/08:08:f0:3f:a4/00:00:00:00:00/40 tag 1 ncq 4096 in
Feb 28 15:24:12 vhs-4 kernel: [ 190.098158] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:24:12 vhs-4 kernel: [ 190.098159] ata2.00: status: { DRDY ERR }
Feb 28 15:24:12 vhs-4 kernel: [ 190.098161] ata2.00: error: { UNC }
Feb 28 15:24:12 vhs-4 kernel: [ 190.099187] ata2.00: configured for UDMA/133
Feb 28 15:24:12 vhs-4 kernel: [ 190.099193] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:24:12 vhs-4 kernel: [ 190.099194] sd 1:0:0:0: [sdb]
Feb 28 15:24:12 vhs-4 kernel: [ 190.099195] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:24:12 vhs-4 kernel: [ 190.099196] sd 1:0:0:0: [sdb]
Feb 28 15:24:12 vhs-4 kernel: [ 190.099197] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:24:12 vhs-4 kernel: [ 190.099199] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:24:12 vhs-4 kernel: [ 190.099200] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:24:12 vhs-4 kernel: [ 190.099204] 00 a4 3f f1
Feb 28 15:24:12 vhs-4 kernel: [ 190.099206] sd 1:0:0:0: [sdb]
Feb 28 15:24:12 vhs-4 kernel: [ 190.099208] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:24:12 vhs-4 kernel: [ 190.099209] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:24:12 vhs-4 kernel: [ 190.099210] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:24:12 vhs-4 kernel: [ 190.099215] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:24:12 vhs-4 kernel: [ 190.099220] ata2: EH complete
Feb 28 15:24:18 vhs-4 kernel: [ 196.114190] ata2.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0
Feb 28 15:24:18 vhs-4 kernel: [ 196.114196] ata2.00: irq_stat 0x40000008
Feb 28 15:24:18 vhs-4 kernel: [ 196.114200] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:24:18 vhs-4 kernel: [ 196.114206] ata2.00: cmd 60/08:90:f0:3f:a4/00:00:00:00:00/40 tag 18 ncq 4096 in
Feb 28 15:24:18 vhs-4 kernel: [ 196.114206] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:24:18 vhs-4 kernel: [ 196.114209] ata2.00: status: { DRDY ERR }
Feb 28 15:24:18 vhs-4 kernel: [ 196.114211] ata2.00: error: { UNC }
Feb 28 15:24:18 vhs-4 kernel: [ 196.115382] ata2.00: configured for UDMA/133
Feb 28 15:24:18 vhs-4 kernel: [ 196.115394] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:24:18 vhs-4 kernel: [ 196.115397] sd 1:0:0:0: [sdb]
Feb 28 15:24:18 vhs-4 kernel: [ 196.115399] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:24:18 vhs-4 kernel: [ 196.115401] sd 1:0:0:0: [sdb]
Feb 28 15:24:18 vhs-4 kernel: [ 196.115402] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:24:18 vhs-4 kernel: [ 196.115413] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:24:18 vhs-4 kernel: [ 196.115413] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:24:18 vhs-4 kernel: [ 196.115418] 00 a4 3f f1
Feb 28 15:24:18 vhs-4 kernel: [ 196.115420] sd 1:0:0:0: [sdb]
Feb 28 15:24:18 vhs-4 kernel: [ 196.115421] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:24:18 vhs-4 kernel: [ 196.115423] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:24:18 vhs-4 kernel: [ 196.115423] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:24:18 vhs-4 kernel: [ 196.115429] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:24:18 vhs-4 kernel: [ 196.115435] ata2: EH complete
Feb 28 15:25:01 vhs-4 CRON[11744]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:25:01 vhs-4 CRON[11745]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:25:01 vhs-4 CRON[11746]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:25:30 vhs-4 kernel: [ 267.616018] ata2.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0
Feb 28 15:25:30 vhs-4 kernel: [ 267.616024] ata2.00: irq_stat 0x40000008
Feb 28 15:25:30 vhs-4 kernel: [ 267.616028] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:25:30 vhs-4 kernel: [ 267.616034] ata2.00: cmd 60/08:20:f0:3f:a4/00:00:00:00:00/40 tag 4 ncq 4096 in
Feb 28 15:25:30 vhs-4 kernel: [ 267.616034] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:25:30 vhs-4 kernel: [ 267.616037] ata2.00: status: { DRDY ERR }
Feb 28 15:25:30 vhs-4 kernel: [ 267.616040] ata2.00: error: { UNC }
Feb 28 15:25:30 vhs-4 kernel: [ 267.617088] ata2.00: configured for UDMA/133
Feb 28 15:25:30 vhs-4 kernel: [ 267.617094] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:25:30 vhs-4 kernel: [ 267.617095] sd 1:0:0:0: [sdb]
Feb 28 15:25:30 vhs-4 kernel: [ 267.617096] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:25:30 vhs-4 kernel: [ 267.617097] sd 1:0:0:0: [sdb]
Feb 28 15:25:30 vhs-4 kernel: [ 267.617098] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:25:30 vhs-4 kernel: [ 267.617100] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:25:30 vhs-4 kernel: [ 267.617101] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:25:30 vhs-4 kernel: [ 267.617105] 00 a4 3f f1
Feb 28 15:25:30 vhs-4 kernel: [ 267.617107] sd 1:0:0:0: [sdb]
Feb 28 15:25:30 vhs-4 kernel: [ 267.617108] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:25:30 vhs-4 kernel: [ 267.617109] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:25:30 vhs-4 kernel: [ 267.617110] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:25:30 vhs-4 kernel: [ 267.617116] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:25:30 vhs-4 kernel: [ 267.617120] ata2: EH complete
Feb 28 15:25:36 vhs-4 kernel: [ 274.024166] ata2.00: exception Emask 0x0 SAct 0x200000 SErr 0x0 action 0x0
Feb 28 15:25:36 vhs-4 kernel: [ 274.024172] ata2.00: irq_stat 0x40000008
Feb 28 15:25:36 vhs-4 kernel: [ 274.024176] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:25:36 vhs-4 kernel: [ 274.024183] ata2.00: cmd 60/08:a8:f0:3f:a4/00:00:00:00:00/40 tag 21 ncq 4096 in
Feb 28 15:25:36 vhs-4 kernel: [ 274.024183] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:25:36 vhs-4 kernel: [ 274.024186] ata2.00: status: { DRDY ERR }
Feb 28 15:25:36 vhs-4 kernel: [ 274.024188] ata2.00: error: { UNC }
Feb 28 15:25:36 vhs-4 kernel: [ 274.025353] ata2.00: configured for UDMA/133
Feb 28 15:25:36 vhs-4 kernel: [ 274.025365] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:25:36 vhs-4 kernel: [ 274.025368] sd 1:0:0:0: [sdb]
Feb 28 15:25:36 vhs-4 kernel: [ 274.025370] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:25:36 vhs-4 kernel: [ 274.025372] sd 1:0:0:0: [sdb]
Feb 28 15:25:36 vhs-4 kernel: [ 274.025373] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:25:36 vhs-4 kernel: [ 274.025377] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:25:36 vhs-4 kernel: [ 274.025379] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:25:36 vhs-4 kernel: [ 274.025388] 00 a4 3f f1
Feb 28 15:25:36 vhs-4 kernel: [ 274.025392] sd 1:0:0:0: [sdb]
Feb 28 15:25:36 vhs-4 kernel: [ 274.025394] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:25:36 vhs-4 kernel: [ 274.025397] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:25:36 vhs-4 kernel: [ 274.025398] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:25:36 vhs-4 kernel: [ 274.025409] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:25:36 vhs-4 kernel: [ 274.025420] ata2: EH complete
Feb 28 15:25:59 vhs-4 kernel: [ 297.026926] ata2.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x0
Feb 28 15:25:59 vhs-4 kernel: [ 297.026932] ata2.00: irq_stat 0x40000008
Feb 28 15:25:59 vhs-4 kernel: [ 297.026936] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:25:59 vhs-4 kernel: [ 297.026942] ata2.00: cmd 60/08:38:f0:3f:a4/00:00:00:00:00/40 tag 7 ncq 4096 in
Feb 28 15:25:59 vhs-4 kernel: [ 297.026942] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:25:59 vhs-4 kernel: [ 297.026945] ata2.00: status: { DRDY ERR }
Feb 28 15:25:59 vhs-4 kernel: [ 297.026947] ata2.00: error: { UNC }
Feb 28 15:25:59 vhs-4 kernel: [ 297.028046] ata2.00: configured for UDMA/133
Feb 28 15:25:59 vhs-4 kernel: [ 297.028055] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:25:59 vhs-4 kernel: [ 297.028058] sd 1:0:0:0: [sdb]
Feb 28 15:25:59 vhs-4 kernel: [ 297.028060] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:25:59 vhs-4 kernel: [ 297.028062] sd 1:0:0:0: [sdb]
Feb 28 15:25:59 vhs-4 kernel: [ 297.028063] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:25:59 vhs-4 kernel: [ 297.028067] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:25:59 vhs-4 kernel: [ 297.028069] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:25:59 vhs-4 kernel: [ 297.028078] 00 a4 3f f1
Feb 28 15:25:59 vhs-4 kernel: [ 297.028082] sd 1:0:0:0: [sdb]
Feb 28 15:25:59 vhs-4 kernel: [ 297.028084] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:25:59 vhs-4 kernel: [ 297.028087] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:25:59 vhs-4 kernel: [ 297.028088] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:25:59 vhs-4 kernel: [ 297.028099] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:25:59 vhs-4 kernel: [ 297.028108] ata2: EH complete
Feb 28 15:26:01 vhs-4 CRON[12497]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:26:06 vhs-4 kernel: [ 304.203649] ata2.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0
Feb 28 15:26:06 vhs-4 kernel: [ 304.203655] ata2.00: irq_stat 0x40000008
Feb 28 15:26:06 vhs-4 kernel: [ 304.203659] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:26:06 vhs-4 kernel: [ 304.203665] ata2.00: cmd 60/08:c0:f0:3f:a4/00:00:00:00:00/40 tag 24 ncq 4096 in
Feb 28 15:26:06 vhs-4 kernel: [ 304.203665] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:26:06 vhs-4 kernel: [ 304.203668] ata2.00: status: { DRDY ERR }
Feb 28 15:26:06 vhs-4 kernel: [ 304.203671] ata2.00: error: { UNC }
Feb 28 15:26:06 vhs-4 kernel: [ 304.204791] ata2.00: configured for UDMA/133
Feb 28 15:26:06 vhs-4 kernel: [ 304.204804] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:26:06 vhs-4 kernel: [ 304.204807] sd 1:0:0:0: [sdb]
Feb 28 15:26:06 vhs-4 kernel: [ 304.204809] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:26:06 vhs-4 kernel: [ 304.204811] sd 1:0:0:0: [sdb]
Feb 28 15:26:06 vhs-4 kernel: [ 304.204813] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:26:06 vhs-4 kernel: [ 304.204817] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:26:06 vhs-4 kernel: [ 304.204818] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:26:06 vhs-4 kernel: [ 304.204827] 00 a4 3f f1
Feb 28 15:26:06 vhs-4 kernel: [ 304.204838] sd 1:0:0:0: [sdb]
Feb 28 15:26:06 vhs-4 kernel: [ 304.204839] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:26:06 vhs-4 kernel: [ 304.204840] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:26:06 vhs-4 kernel: [ 304.204841] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:26:06 vhs-4 kernel: [ 304.204847] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:26:06 vhs-4 kernel: [ 304.204853] ata2: EH complete
Feb 28 15:26:24 vhs-4 postfix/sendmail[13227]: fatal: open /etc/postfix/main.cf: No such file or directory
Feb 28 15:26:59 vhs-4 kernel: [ 356.505352] ata2.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
Feb 28 15:26:59 vhs-4 kernel: [ 356.505358] ata2.00: irq_stat 0x40000008
Feb 28 15:26:59 vhs-4 kernel: [ 356.505362] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:26:59 vhs-4 kernel: [ 356.505369] ata2.00: cmd 60/08:b0:f0:3f:a4/00:00:00:00:00/40 tag 22 ncq 4096 in
Feb 28 15:26:59 vhs-4 kernel: [ 356.505369] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:26:59 vhs-4 kernel: [ 356.505372] ata2.00: status: { DRDY ERR }
Feb 28 15:26:59 vhs-4 kernel: [ 356.505374] ata2.00: error: { UNC }
Feb 28 15:26:59 vhs-4 kernel: [ 356.506553] ata2.00: configured for UDMA/133
Feb 28 15:26:59 vhs-4 kernel: [ 356.506565] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:26:59 vhs-4 kernel: [ 356.506568] sd 1:0:0:0: [sdb]
Feb 28 15:26:59 vhs-4 kernel: [ 356.506570] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:26:59 vhs-4 kernel: [ 356.506572] sd 1:0:0:0: [sdb]
Feb 28 15:26:59 vhs-4 kernel: [ 356.506574] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:26:59 vhs-4 kernel: [ 356.506578] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:26:59 vhs-4 kernel: [ 356.506579] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:26:59 vhs-4 kernel: [ 356.506588] 00 a4 3f f1
Feb 28 15:26:59 vhs-4 kernel: [ 356.506592] sd 1:0:0:0: [sdb]
Feb 28 15:26:59 vhs-4 kernel: [ 356.506595] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:26:59 vhs-4 kernel: [ 356.506597] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:26:59 vhs-4 kernel: [ 356.506606] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:26:59 vhs-4 kernel: [ 356.506611] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:26:59 vhs-4 kernel: [ 356.506625] ata2: EH complete
Feb 28 15:27:02 vhs-4 kernel: [ 359.687302] ata2.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0
Feb 28 15:27:02 vhs-4 kernel: [ 359.687308] ata2.00: irq_stat 0x40000008
Feb 28 15:27:02 vhs-4 kernel: [ 359.687312] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:27:02 vhs-4 kernel: [ 359.687319] ata2.00: cmd 60/08:40:f0:3f:a4/00:00:00:00:00/40 tag 8 ncq 4096 in
Feb 28 15:27:02 vhs-4 kernel: [ 359.687319] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:27:02 vhs-4 kernel: [ 359.687322] ata2.00: status: { DRDY ERR }
Feb 28 15:27:02 vhs-4 kernel: [ 359.687324] ata2.00: error: { UNC }
Feb 28 15:27:02 vhs-4 kernel: [ 359.688370] ata2.00: configured for UDMA/133
Feb 28 15:27:02 vhs-4 kernel: [ 359.688380] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:27:02 vhs-4 kernel: [ 359.688383] sd 1:0:0:0: [sdb]
Feb 28 15:27:02 vhs-4 kernel: [ 359.688384] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:27:02 vhs-4 kernel: [ 359.688386] sd 1:0:0:0: [sdb]
Feb 28 15:27:02 vhs-4 kernel: [ 359.688388] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:27:02 vhs-4 kernel: [ 359.688392] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:27:02 vhs-4 kernel: [ 359.688394] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:27:02 vhs-4 kernel: [ 359.688403] 00 a4 3f f1
Feb 28 15:27:02 vhs-4 kernel: [ 359.688407] sd 1:0:0:0: [sdb]
Feb 28 15:27:02 vhs-4 kernel: [ 359.688409] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:27:02 vhs-4 kernel: [ 359.688411] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:27:02 vhs-4 kernel: [ 359.688413] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:27:02 vhs-4 kernel: [ 359.688424] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:27:02 vhs-4 kernel: [ 359.688432] ata2: EH complete
Feb 28 15:27:02 vhs-4 afpd[6818]: AFP Server shutting down on SIGTERM
Feb 28 15:27:02 vhs-4 kernel: [ 360.103854] init: vht/backup main process (4209) killed by TERM signal
Feb 28 15:27:02 vhs-4 kernel: [ 360.104353] init: vsftpd main process (6805) killed by TERM signal
Feb 28 15:27:02 vhs-4 kernel: [ 360.120192] init: smbd main process (7186) killed by TERM signal
Feb 28 15:27:02 vhs-4 rpc.mountd[7661]: Caught signal 15, un-registering and exiting.
Feb 28 15:27:02 vhs-4 kernel: [ 360.139433] nfsd: last server has exited, flushing export cache
Feb 28 15:27:02 vhs-4 console-kit-daemon[7897]: GLib-CRITICAL: Source ID 12 was not found when attempting to remove it
Feb 28 15:27:02 vhs-4 rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Feb 28 15:27:02 vhs-4 kernel: [ 360.262671] init: rpcbind main process (7172) terminated with status 2
Feb 28 15:27:03 vhs-4 kernel: [ 361.141652] init: vht/xbmc main process (7889) terminated with status 1
Feb 28 15:27:06 vhs-4 kernel: [ 364.378347] init: vht/btsync main process (6804) killed by KILL signal
Feb 28 15:27:07 vhs-4 kernel: [ 364.518355] init: forked-daapd main process (4065) killed by KILL signal
Feb 28 15:27:13 vhs-4 kernel: [ 371.410154] init: vht/indexer main process (5990) killed by KILL signal
Feb 28 15:27:20 vhs-4 kernel: [ 377.494689] ata2.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0
Feb 28 15:27:20 vhs-4 kernel: [ 377.494693] ata2.00: irq_stat 0x40000008
Feb 28 15:27:20 vhs-4 kernel: [ 377.494695] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:27:20 vhs-4 kernel: [ 377.494698] ata2.00: cmd 60/08:88:f0:3f:a4/00:00:00:00:00/40 tag 17 ncq 4096 in
Feb 28 15:27:20 vhs-4 kernel: [ 377.494698] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:27:20 vhs-4 kernel: [ 377.494700] ata2.00: status: { DRDY ERR }
Feb 28 15:27:20 vhs-4 kernel: [ 377.494701] ata2.00: error: { UNC }
Feb 28 15:27:20 vhs-4 kernel: [ 377.495814] ata2.00: configured for UDMA/133
Feb 28 15:27:20 vhs-4 kernel: [ 377.495821] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:27:20 vhs-4 kernel: [ 377.495825] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 377.495827] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:27:20 vhs-4 kernel: [ 377.495835] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 377.495836] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:27:20 vhs-4 kernel: [ 377.495838] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:27:20 vhs-4 kernel: [ 377.495839] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:27:20 vhs-4 kernel: [ 377.495844] 00 a4 3f f1
Feb 28 15:27:20 vhs-4 kernel: [ 377.495847] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 377.495848] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:27:20 vhs-4 kernel: [ 377.495850] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:27:20 vhs-4 kernel: [ 377.495851] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:27:20 vhs-4 kernel: [ 377.495857] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:27:20 vhs-4 kernel: [ 377.495860] Buffer I/O error on device sdb2, logical block 1220862
Feb 28 15:27:20 vhs-4 kernel: [ 377.495867] ata2: EH complete
Feb 28 15:27:20 vhs-4 kernel: [ 377.674946] ata2.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0
Feb 28 15:27:20 vhs-4 kernel: [ 377.674952] ata2.00: irq_stat 0x40000008
Feb 28 15:27:20 vhs-4 kernel: [ 377.674956] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:27:20 vhs-4 kernel: [ 377.674963] ata2.00: cmd 60/08:90:f0:3f:a4/00:00:00:00:00/40 tag 18 ncq 4096 in
Feb 28 15:27:20 vhs-4 kernel: [ 377.674963] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:27:20 vhs-4 kernel: [ 377.674966] ata2.00: status: { DRDY ERR }
Feb 28 15:27:20 vhs-4 kernel: [ 377.674968] ata2.00: error: { UNC }
Feb 28 15:27:20 vhs-4 kernel: [ 377.676162] ata2.00: configured for UDMA/133
Feb 28 15:27:20 vhs-4 kernel: [ 377.676175] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:27:20 vhs-4 kernel: [ 377.676178] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 377.676180] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:27:20 vhs-4 kernel: [ 377.676182] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 377.676184] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:27:20 vhs-4 kernel: [ 377.676187] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:27:20 vhs-4 kernel: [ 377.676189] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:27:20 vhs-4 kernel: [ 377.676198] 00 a4 3f f1
Feb 28 15:27:20 vhs-4 kernel: [ 377.676202] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 377.676205] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:27:20 vhs-4 kernel: [ 377.676207] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:27:20 vhs-4 kernel: [ 377.676209] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:27:20 vhs-4 kernel: [ 377.676219] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:27:20 vhs-4 kernel: [ 377.676223] Buffer I/O error on device sdb2, logical block 1220862
Feb 28 15:27:20 vhs-4 kernel: [ 377.676236] ata2: EH complete
Feb 28 15:27:20 vhs-4 kernel: [ 378.351349] ata2.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x0
Feb 28 15:27:20 vhs-4 kernel: [ 378.351354] ata2.00: irq_stat 0x40000008
Feb 28 15:27:20 vhs-4 kernel: [ 378.351358] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:27:20 vhs-4 kernel: [ 378.351365] ata2.00: cmd 60/08:90:f0:3f:a4/00:00:00:00:00/40 tag 18 ncq 4096 in
Feb 28 15:27:20 vhs-4 kernel: [ 378.351365] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:27:20 vhs-4 kernel: [ 378.351368] ata2.00: status: { DRDY ERR }
Feb 28 15:27:20 vhs-4 kernel: [ 378.351370] ata2.00: error: { UNC }
Feb 28 15:27:20 vhs-4 kernel: [ 378.352669] ata2.00: configured for UDMA/133
Feb 28 15:27:20 vhs-4 kernel: [ 378.352682] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:27:20 vhs-4 kernel: [ 378.352685] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 378.352687] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:27:20 vhs-4 kernel: [ 378.352689] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 378.352691] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:27:20 vhs-4 kernel: [ 378.352695] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:27:20 vhs-4 kernel: [ 378.352696] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:27:20 vhs-4 kernel: [ 378.352705] 00 a4 3f f1
Feb 28 15:27:20 vhs-4 kernel: [ 378.352709] sd 1:0:0:0: [sdb]
Feb 28 15:27:20 vhs-4 kernel: [ 378.352712] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:27:20 vhs-4 kernel: [ 378.352714] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:27:20 vhs-4 kernel: [ 378.352716] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:27:20 vhs-4 kernel: [ 378.352727] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:27:20 vhs-4 kernel: [ 378.352731] Buffer I/O error on device sdb2, logical block 1220862
Feb 28 15:27:20 vhs-4 kernel: [ 378.352747] ata2: EH complete
Feb 28 15:27:21 vhs-4 kernel: [ 378.531518] ata2.00: exception Emask 0x0 SAct 0x300000 SErr 0x0 action 0x0
Feb 28 15:27:21 vhs-4 kernel: [ 378.531524] ata2.00: irq_stat 0x40000008
Feb 28 15:27:21 vhs-4 kernel: [ 378.531528] ata2.00: failed command: READ FPDMA QUEUED
Feb 28 15:27:21 vhs-4 kernel: [ 378.531535] ata2.00: cmd 60/08:a8:f0:3f:a4/00:00:00:00:00/40 tag 21 ncq 4096 in
Feb 28 15:27:21 vhs-4 kernel: [ 378.531535] res 41/40:00:f1:3f:a4/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Feb 28 15:27:21 vhs-4 kernel: [ 378.531538] ata2.00: status: { DRDY ERR }
Feb 28 15:27:21 vhs-4 kernel: [ 378.531540] ata2.00: error: { UNC }
Feb 28 15:27:21 vhs-4 kernel: [ 378.533463] ata2.00: configured for UDMA/133
Feb 28 15:27:21 vhs-4 kernel: [ 378.533478] sd 1:0:0:0: [sdb] Unhandled sense code
Feb 28 15:27:21 vhs-4 kernel: [ 378.533481] sd 1:0:0:0: [sdb]
Feb 28 15:27:21 vhs-4 kernel: [ 378.533483] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 15:27:21 vhs-4 kernel: [ 378.533485] sd 1:0:0:0: [sdb]
Feb 28 15:27:21 vhs-4 kernel: [ 378.533487] Sense Key : Medium Error [current] [descriptor]
Feb 28 15:27:21 vhs-4 kernel: [ 378.533491] Descriptor sense data with sense descriptors (in hex):
Feb 28 15:27:21 vhs-4 kernel: [ 378.533492] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 15:27:21 vhs-4 kernel: [ 378.533501] 00 a4 3f f1
Feb 28 15:27:21 vhs-4 kernel: [ 378.533505] sd 1:0:0:0: [sdb]
Feb 28 15:27:21 vhs-4 kernel: [ 378.533508] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 15:27:21 vhs-4 kernel: [ 378.533510] sd 1:0:0:0: [sdb] CDB:
Feb 28 15:27:21 vhs-4 kernel: [ 378.533512] Read(16): 88 00 00 00 00 00 00 a4 3f f0 00 00 00 08 00 00
Feb 28 15:27:21 vhs-4 kernel: [ 378.533523] end_request: I/O error, dev sdb, sector 10764273
Feb 28 15:27:21 vhs-4 kernel: [ 378.533527] Buffer I/O error on device sdb2, logical block 1220862
Feb 28 15:27:21 vhs-4 kernel: [ 378.533539] ata2: EH complete
Feb 28 15:27:25 vhs-4 kernel: [ 382.492337] Adding 498024k swap on /dev/sdb1. Priority:-4 extents:1 across:498024k FS
Feb 28 15:27:25 vhs-4 kernel: [ 382.527379] md: bind<sdb2>
Feb 28 15:27:25 vhs-4 kernel: [ 382.573318] RAID1 conf printout:
Feb 28 15:27:25 vhs-4 kernel: [ 382.573321] --- wd:3 rd:3
Feb 28 15:27:25 vhs-4 kernel: [ 382.573323] disk 0, wo:0, o:1, dev:sda2
Feb 28 15:27:25 vhs-4 kernel: [ 382.573325] disk 1, wo:0, o:1, dev:sdc2
Feb 28 15:27:25 vhs-4 kernel: [ 382.573326] disk 2, wo:0, o:1, dev:sdd2
Feb 28 15:27:30 vhs-4 kernel: [ 387.638014] RAID1 conf printout:
Feb 28 15:27:30 vhs-4 kernel: [ 387.638017] --- wd:3 rd:4
Feb 28 15:27:30 vhs-4 kernel: [ 387.638019] disk 0, wo:0, o:1, dev:sda2
Feb 28 15:27:30 vhs-4 kernel: [ 387.638020] disk 1, wo:0, o:1, dev:sdc2
Feb 28 15:27:30 vhs-4 kernel: [ 387.638021] disk 2, wo:0, o:1, dev:sdd2
Feb 28 15:27:30 vhs-4 kernel: [ 387.638023] disk 3, wo:1, o:1, dev:sdb2
Feb 28 15:27:30 vhs-4 kernel: [ 387.638129] md: recovery of RAID array md0
Feb 28 15:27:30 vhs-4 kernel: [ 387.638131] md: minimum _guaranteed_ speed: 50000 KB/sec/disk.
Feb 28 15:27:30 vhs-4 kernel: [ 387.638132] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Feb 28 15:27:30 vhs-4 kernel: [ 387.638134] md: using 128k window, over a total of 4883392k.
Feb 28 15:28:01 vhs-4 CRON[15865]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:30:01 vhs-4 CRON[17943]: (root) CMD (/opt/vht/bin/storage/hddSmartChecker.php --smart)
Feb 28 15:30:01 vhs-4 CRON[17945]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:30:01 vhs-4 CRON[17946]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:30:01 vhs-4 CRON[17947]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:30:01 vhs-4 CRON[17952]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:30:02 vhs-4 kernel: [ 539.673992] md: md0: recovery done.
Feb 28 15:30:02 vhs-4 kernel: [ 539.758080] RAID1 conf printout:
Feb 28 15:30:02 vhs-4 kernel: [ 539.758083] --- wd:4 rd:4
Feb 28 15:30:02 vhs-4 kernel: [ 539.758086] disk 0, wo:0, o:1, dev:sda2
Feb 28 15:30:02 vhs-4 kernel: [ 539.758087] disk 1, wo:0, o:1, dev:sdc2
Feb 28 15:30:02 vhs-4 kernel: [ 539.758089] disk 2, wo:0, o:1, dev:sdd2
Feb 28 15:30:02 vhs-4 kernel: [ 539.758090] disk 3, wo:0, o:1, dev:sdb2
Feb 28 15:30:04 vhs-4 kernel: [ 542.493162] md: bind<sdb3>
Feb 28 15:30:04 vhs-4 kernel: [ 542.542537] RAID conf printout:
Feb 28 15:30:04 vhs-4 kernel: [ 542.542541] --- level:5 rd:4 wd:3
Feb 28 15:30:04 vhs-4 kernel: [ 542.542543] disk 0, o:1, dev:sda3
Feb 28 15:30:04 vhs-4 kernel: [ 542.542544] disk 1, o:1, dev:sdb3
Feb 28 15:30:04 vhs-4 kernel: [ 542.542545] disk 2, o:1, dev:sdc3
Feb 28 15:30:04 vhs-4 kernel: [ 542.542546] disk 3, o:1, dev:sdd3
Feb 28 15:30:04 vhs-4 kernel: [ 542.542584] md: recovery of RAID array md3
Feb 28 15:30:04 vhs-4 kernel: [ 542.542586] md: minimum _guaranteed_ speed: 50000 KB/sec/disk.
Feb 28 15:30:04 vhs-4 kernel: [ 542.542587] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Feb 28 15:30:04 vhs-4 kernel: [ 542.542590] md: using 128k window, over a total of 2924883776k.
Feb 28 15:30:05 vhs-4 mdadm[4028]: RebuildStarted event detected on md device /dev/md3
Feb 28 15:32:01 vhs-4 CRON[20141]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:34:01 vhs-4 CRON[21782]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:35:01 vhs-4 CRON[22642]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:35:01 vhs-4 CRON[22643]: (root) CMD (/opt/vht/bin/tv/tvUpdateLaunch.sh)
Feb 28 15:35:01 vhs-4 CRON[22645]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:35:01 vhs-4 CRON[22647]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:36:01 vhs-4 CRON[23467]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:38:01 vhs-4 CRON[25312]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:40:01 vhs-4 CRON[26814]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:40:01 vhs-4 CRON[26815]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:40:01 vhs-4 CRON[26816]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:40:01 vhs-4 CRON[26819]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:42:01 vhs-4 CRON[28194]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:44:01 vhs-4 CRON[29541]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:45:01 vhs-4 CRON[30577]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:45:01 vhs-4 CRON[30579]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:45:01 vhs-4 CRON[30580]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:46:01 vhs-4 CRON[31334]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:48:01 vhs-4 CRON[511]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:50:01 vhs-4 CRON[2079]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:50:01 vhs-4 CRON[2080]: (root) CMD (/opt/vht/bin/tv/tvUpdateLaunch.sh)
Feb 28 15:50:01 vhs-4 CRON[2082]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:50:01 vhs-4 CRON[2089]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:50:01 vhs-4 CRON[2086]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:52:01 vhs-4 CRON[4033]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:54:01 vhs-4 CRON[5766]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:55:01 vhs-4 CRON[6499]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 15:55:01 vhs-4 CRON[6501]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 15:55:01 vhs-4 CRON[6502]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 15:56:01 vhs-4 CRON[7284]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:58:01 vhs-4 CRON[8684]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 15:58:31 vhs-4 kernel: [ 2251.244193] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: acl
Feb 28 15:58:32 vhs-4 postfix/sendmail[9435]: fatal: open /etc/postfix/main.cf: No such file or directory
Feb 28 15:58:32 vhs-4 postfix/sendmail[9446]: fatal: open /etc/postfix/main.cf: No such file or directory
Feb 28 15:58:45 vhs-4 kernel: [ 2265.172762] init: apache2-users main process ended, respawning
Feb 28 15:59:24 vhs-4 kernel: [ 2304.379555] init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
Feb 28 15:59:24 vhs-4 statd-pre-start: started
Feb 28 15:59:24 vhs-4 sm-notify[12066]: Version 1.2.8 starting
Feb 28 15:59:24 vhs-4 sm-notify[12066]: Already notifying clients; Exiting!
Feb 28 15:59:25 vhs-4 rpc.statd[12080]: Version 1.2.8 starting
Feb 28 15:59:25 vhs-4 rpc.statd[12080]: Flags: TI-RPC
Feb 28 15:59:25 vhs-4 kernel: [ 2304.587481] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Feb 28 15:59:25 vhs-4 kernel: [ 2304.587496] NFSD: starting 90-second grace period (net ffffffff81cd3440)
Feb 28 15:59:25 vhs-4 afpd[12079]: main: atp_open: Cannot assign requested address
Feb 28 15:59:25 vhs-4 rpc.mountd[12236]: Version 1.2.8 starting
Feb 28 15:59:25 vhs-4 afpd[12079]: AFP/TCP started, advertising 192.168.0.144:548 (2.2.4)
Feb 28 15:59:25 vhs-4 smbd[12069]: [2023/02/28 15:59:25.331956, 0] smbd/server.c:1128(main)
Feb 28 15:59:25 vhs-4 smbd[12069]: standard input is not a socket, assuming -D option
Feb 28 15:59:25 vhs-4 kernel: [ 2305.415119] init: Failed to spawn vht/transmission-notify main process: unable to execute: No such file or directory
Feb 28 15:59:26 vhs-4 dnsmasq[8042]: read /etc/hosts - 8 addresses
Feb 28 15:59:26 vhs-4 dnsmasq[8042]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Feb 28 15:59:26 vhs-4 dnsmasq-dhcp[8042]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Feb 28 15:59:29 vhs-4 www-browser: *** err
Feb 28 15:59:29 vhs-4 www-browser: /dev/pts/22: Permission denied
Feb 28 15:59:29 vhs-4 www-browser: *** err
Feb 28 15:59:29 vhs-4 www-browser: Oh, oh, it's an error! possibly I die!
Feb 28 15:59:30 vhs-4 acpid: client 7987[0:0] has disconnected
Feb 28 15:59:30 vhs-4 acpid: client connected from 13782[0:0]
Feb 28 15:59:30 vhs-4 acpid: 1 client rule loaded
Feb 28 16:00:01 vhs-4 CRON[14408]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 16:00:01 vhs-4 CRON[14409]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 16:00:01 vhs-4 CRON[14411]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 16:00:01 vhs-4 CRON[14410]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 16:02:01 vhs-4 CRON[16578]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 16:04:01 vhs-4 CRON[19117]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286808] ata5.00: exception Emask 0x0 SAct 0x7800 SErr 0x0 action 0x0
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286814] ata5.00: irq_stat 0x40000008
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286818] ata5.00: failed command: READ FPDMA QUEUED
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286824] ata5.00: cmd 60/d8:58:80:79:1b/03:00:07:00:00/40 tag 11 ncq 503808 in
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286824] res 41/40:00:68:7c:1b/00:00:07:00:00/40 Emask 0x409 (media error) <F>
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286827] ata5.00: status: { DRDY ERR }
Feb 28 16:04:07 vhs-4 kernel: [ 2587.286829] ata5.00: error: { UNC }
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289071] ata5.00: configured for UDMA/133
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289121] sd 4:0:0:0: [sdc] Unhandled sense code
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289124] sd 4:0:0:0: [sdc]
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289126] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289128] sd 4:0:0:0: [sdc]
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289129] Sense Key : Medium Error [current] [descriptor]
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289133] Descriptor sense data with sense descriptors (in hex):
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289135] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289144] 07 1b 7c 68
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289148] sd 4:0:0:0: [sdc]
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289151] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289153] sd 4:0:0:0: [sdc] CDB:
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289154] Read(16): 88 00 00 00 00 00 07 1b 79 80 00 00 03 d8 00 00
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289171] end_request: I/O error, dev sdc, sector 119241832
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289173] md/raid:md3: read error not correctable (sector 108478160 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289175] md/raid:md3: read error not correctable (sector 108478168 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289176] md/raid:md3: read error not correctable (sector 108478176 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289177] md/raid:md3: read error not correctable (sector 108478184 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289178] md/raid:md3: read error not correctable (sector 108478192 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289179] md/raid:md3: read error not correctable (sector 108478200 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289180] md/raid:md3: read error not correctable (sector 108478208 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289181] md/raid:md3: read error not correctable (sector 108478216 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289182] md/raid:md3: read error not correctable (sector 108478224 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289183] md/raid:md3: read error not correctable (sector 108478232 on sdc3).
Feb 28 16:04:07 vhs-4 kernel: [ 2587.289198] ata5: EH complete
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246230] ata5.00: exception Emask 0x0 SAct 0x40000003 SErr 0x0 action 0x0
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246236] ata5.00: irq_stat 0x40000008
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246241] ata5.00: failed command: READ FPDMA QUEUED
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246247] ata5.00: cmd 60/f0:f0:68:7c:1b/00:00:07:00:00/40 tag 30 ncq 122880 in
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246247] res 41/40:00:68:7c:1b/00:00:07:00:00/40 Emask 0x409 (media error) <F>
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246250] ata5.00: status: { DRDY ERR }
Feb 28 16:04:10 vhs-4 kernel: [ 2590.246252] ata5.00: error: { UNC }
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247747] ata5.00: configured for UDMA/133
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247774] sd 4:0:0:0: [sdc] Unhandled sense code
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247777] sd 4:0:0:0: [sdc]
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247779] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247782] sd 4:0:0:0: [sdc]
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247783] Sense Key : Medium Error [current] [descriptor]
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247787] Descriptor sense data with sense descriptors (in hex):
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247789] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247798] 07 1b 7c 68
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247808] sd 4:0:0:0: [sdc]
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247809] Add. Sense: Unrecovered read error - auto reallocate failed
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247810] sd 4:0:0:0: [sdc] CDB:
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247811] Read(16): 88 00 00 00 00 00 07 1b 7c 68 00 00 00 f0 00 00
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247817] end_request: I/O error, dev sdc, sector 119241832
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247821] md/raid:md3: Disk failure on sdc3, disabling device.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247821] md/raid:md3: Operation continuing on 2 devices.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247858] ata5: EH complete
Feb 28 16:04:10 vhs-4 kernel: [ 2590.327783] Aborting journal on device md3-8.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.327817] Buffer I/O error on device md3, logical block 1096843264
Feb 28 16:04:10 vhs-4 kernel: [ 2590.327819] lost page write due to I/O error on md3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.327825] JBD2: Error -5 detected when updating journal superblock for md3-8.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329621] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443419337, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329687] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443419339, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329714] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443419343, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329737] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443419335, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329760] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443419333, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329872] md: md3: recovery interrupted.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329894] EXT4-fs warning (device md3): ext4_end_bio:317: I/O error -5 writing to inode 426246739 (offset 0 size 0 starting block 1705017752)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.329896] Buffer I/O error on device md3, logical block 1705017752
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531270] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443419345, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531273] RAID conf printout:
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531274] --- level:5 rd:4 wd:2
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531276] disk 0, o:1, dev:sda3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531278] disk 1, o:1, dev:sdb3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531279] disk 2, o:0, dev:sdc3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.531281] disk 3, o:1, dev:sdd3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538240] RAID conf printout:
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538243] --- level:5 rd:4 wd:2
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538245] disk 0, o:1, dev:sda3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538246] disk 2, o:0, dev:sdc3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538247] disk 3, o:1, dev:sdd3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538259] RAID conf printout:
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538260] --- level:5 rd:4 wd:2
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538261] disk 0, o:1, dev:sda3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538262] disk 2, o:0, dev:sdc3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.538263] disk 3, o:1, dev:sdd3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.546284] RAID conf printout:
Feb 28 16:04:10 vhs-4 kernel: [ 2590.546287] --- level:5 rd:4 wd:2
Feb 28 16:04:10 vhs-4 kernel: [ 2590.546288] disk 0, o:1, dev:sda3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.546289] disk 3, o:1, dev:sdd3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610614] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610619] lost page write due to I/O error on md3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610685] EXT4-fs error (device md3): ext4_journal_check_start:56:
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610685] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443418941, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610688] Detected aborted journal
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610690] EXT4-fs (md3): Remounting filesystem read-only
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610692] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610721] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610722] lost page write due to I/O error on md3
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610739] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443418917, block 0)
Feb 28 16:04:10 vhs-4 kernel: [ 2590.610771] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 443418943, block 0)
Feb 28 16:04:11 vhs-4 kernel: [ 2591.289639] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072107: block 1776287786: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.289644] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.422741] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:11 vhs-4 kernel: [ 2591.422744] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.423185] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072105: block 1776287786: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.423188] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.434078] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:11 vhs-4 kernel: [ 2591.434082] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.446756] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072103: block 1776287786: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.446759] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.446805] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:11 vhs-4 kernel: [ 2591.446807] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471224] Buffer I/O error on device md3, logical block 407
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471227] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471231] Buffer I/O error on device md3, logical block 408
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471232] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471261] Buffer I/O error on device md3, logical block 454
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471262] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471265] Buffer I/O error on device md3, logical block 472
Feb 28 16:04:11 vhs-4 kernel: [ 2591.471266] lost page write due to I/O error on md3
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498228] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072109: block 1776287786: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498230] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498289] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072113: block 1776287787: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498291] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498450] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072111: block 1776287786: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498452] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498520] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #444072115: block 1776287787: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498522] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498576] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #443419617: block 1773666526: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498577] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498640] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #443419667: block 1773666529: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 kernel: [ 2591.498684] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #443419728: block 1773666532: comm du: unable to read itable block
Feb 28 16:04:11 vhs-4 postfix/sendmail[19325]: fatal: open /etc/postfix/main.cf: No such file or directory
Feb 28 16:04:12 vhs-4 mdadm[4028]: Fail event detected on md device /dev/md3, component device /dev/sdc3
Feb 28 16:04:12 vhs-4 mdadm[4028]: RebuildFinished event detected on md device /dev/md3
Feb 28 16:04:15 vhs-4 kernel: [ 2595.560711] EXT4-fs warning: 34 callbacks suppressed
Feb 28 16:04:15 vhs-4 kernel: [ 2595.560716] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 444073454, block 0)
Feb 28 16:04:15 vhs-4 kernel: [ 2595.665293] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 444073605, block 0)
Feb 28 16:04:15 vhs-4 kernel: [ 2595.741746] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 445647519, block 0)
Feb 28 16:04:15 vhs-4 kernel: [ 2595.741816] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 445647540, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.013695] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 472515827, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.013740] EXT4-fs: 56 callbacks suppressed
Feb 28 16:04:16 vhs-4 kernel: [ 2596.013742] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161353] quiet_error: 70 callbacks suppressed
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161357] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161358] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161713] EXT4-fs warning (device md3): __ext4_read_dirblock:675: error reading directory block (ino 102105626, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161871] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161881] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161884] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161953] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 426246443, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.161999] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 426246438, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.162016] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 426246439, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.162115] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.162121] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.162122] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178075] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178089] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178092] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178304] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178312] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178314] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178398] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178404] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178405] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178449] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178455] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178457] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178507] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178513] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178514] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178571] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 426246735, block 0)
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178614] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178620] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178621] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178670] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178676] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:16 vhs-4 kernel: [ 2596.178677] lost page write due to I/O error on md3
Feb 28 16:04:16 vhs-4 kernel: [ 2596.677583] EXT4-fs error: 65 callbacks suppressed
Feb 28 16:04:16 vhs-4 kernel: [ 2596.677588] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110706: block 1876427035: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804411] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110654: block 1876427031: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804533] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110735: block 1876427036: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804617] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110751: block 1876427037: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804710] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110670: block 1876427032: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804807] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110689: block 1876427034: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804884] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110783: block 1876427039: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.804990] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110685: block 1876427033: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.805054] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110531: block 1876427024: comm du: unable to read itable block
Feb 28 16:04:17 vhs-4 kernel: [ 2596.805110] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #469110767: block 1876427038: comm du: unable to read itable block
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673699] EXT4-fs warning: 69466 callbacks suppressed
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673703] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673727] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673756] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673784] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673803] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673822] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673840] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673859] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673877] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:20 vhs-4 kernel: [ 2600.673897] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:21 vhs-4 kernel: [ 2601.305349] EXT4-fs: 445 callbacks suppressed
Feb 28 16:04:21 vhs-4 kernel: [ 2601.305353] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.411569] quiet_error: 445 callbacks suppressed
Feb 28 16:04:21 vhs-4 kernel: [ 2601.411572] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.411574] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.411715] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.447700] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.447702] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.447887] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.447913] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.447916] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448076] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448085] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448088] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448150] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448159] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448162] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448222] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448232] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448234] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448292] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448302] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448305] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448367] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448377] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448380] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448450] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448460] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448463] lost page write due to I/O error on md3
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448512] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448519] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:21 vhs-4 kernel: [ 2601.448520] lost page write due to I/O error on md3
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811011] EXT4-fs error: 7829 callbacks suppressed
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811015] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811068] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811118] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811169] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811219] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811269] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811319] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811370] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811421] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:22 vhs-4 kernel: [ 2601.811472] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:26 vhs-4 kernel: [ 2606.358915] EXT4-fs warning: 30182 callbacks suppressed
Feb 28 16:04:26 vhs-4 kernel: [ 2606.358919] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.358945] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.358968] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.358991] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.359014] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.359037] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.359059] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.359082] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.359105] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:26 vhs-4 kernel: [ 2606.359128] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:28 vhs-4 kernel: [ 2608.486694] EXT4-fs error: 92474 callbacks suppressed
Feb 28 16:04:28 vhs-4 kernel: [ 2608.486699] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.486711] EXT4-fs: 99869 callbacks suppressed
Feb 28 16:04:28 vhs-4 kernel: [ 2608.486713] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.547731] quiet_error: 99869 callbacks suppressed
Feb 28 16:04:28 vhs-4 kernel: [ 2608.547734] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.547735] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.547887] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.547890] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597577] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597580] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597664] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597666] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597672] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597673] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597716] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597718] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597723] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597724] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597765] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597766] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597771] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597772] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597812] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597814] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597819] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597819] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597859] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597861] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597865] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597866] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597906] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597908] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597912] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597913] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597953] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597954] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597959] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.597960] lost page write due to I/O error on md3
Feb 28 16:04:28 vhs-4 kernel: [ 2608.598000] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:28 vhs-4 kernel: [ 2608.598002] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:28 vhs-4 kernel: [ 2608.598007] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:28 vhs-4 kernel: [ 2608.598008] lost page write due to I/O error on md3
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476439] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476443] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476466] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476488] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476509] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476531] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476552] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476573] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476595] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476616] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:33 vhs-4 kernel: [ 2613.476637] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:35 vhs-4 kernel: [ 2615.564704] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:04:35 vhs-4 kernel: [ 2615.564708] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.564711] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:04:35 vhs-4 kernel: [ 2615.564712] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.611203] quiet_error: 99990 callbacks suppressed
Feb 28 16:04:35 vhs-4 kernel: [ 2615.611205] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.611207] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.611316] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.611320] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.638784] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.638788] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.638983] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.638986] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639013] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639016] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639108] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639110] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639117] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639119] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639177] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639178] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639186] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639188] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639245] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639246] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639254] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639256] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639307] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639308] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639315] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639316] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639362] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639364] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639369] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639371] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639416] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639417] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639423] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639424] lost page write due to I/O error on md3
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639470] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639472] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639477] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:35 vhs-4 kernel: [ 2615.639478] lost page write due to I/O error on md3
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620514] EXT4-fs error: 99800 callbacks suppressed
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620518] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620520] EXT4-fs: 99800 callbacks suppressed
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620522] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620577] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620579] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620633] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620634] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620688] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620690] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620743] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620745] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620799] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620801] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620854] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620856] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620910] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620911] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620966] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.620967] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.621021] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:40 vhs-4 kernel: [ 2620.621023] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:40 vhs-4 kernel: [ 2620.629968] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:04:40 vhs-4 kernel: [ 2620.629970] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.629990] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630009] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630028] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630047] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630066] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630084] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630103] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630122] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:40 vhs-4 kernel: [ 2620.630167] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:43 vhs-4 kernel: [ 2622.841453] quiet_error: 99990 callbacks suppressed
Feb 28 16:04:43 vhs-4 kernel: [ 2622.841456] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.841458] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869022] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869026] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869200] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869203] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869286] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869288] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869362] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869364] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869438] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869440] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869513] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869515] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869589] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869591] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869656] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869658] lost page write due to I/O error on md3
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869707] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:43 vhs-4 kernel: [ 2622.869708] lost page write due to I/O error on md3
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630247] EXT4-fs error: 55803 callbacks suppressed
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630252] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630254] EXT4-fs: 55803 callbacks suppressed
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630255] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630312] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630313] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630366] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630368] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630422] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630424] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630478] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630479] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630533] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630535] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630589] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630591] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630645] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630646] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630704] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630705] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630756] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:45 vhs-4 kernel: [ 2625.630757] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778263] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778266] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778287] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778306] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778325] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778343] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778362] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778380] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778398] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778416] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:47 vhs-4 kernel: [ 2627.778435] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:50 vhs-4 kernel: [ 2630.004878] quiet_error: 99990 callbacks suppressed
Feb 28 16:04:50 vhs-4 kernel: [ 2630.004882] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.004884] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032528] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032532] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032680] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032681] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032734] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032735] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032784] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032785] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032834] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032835] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032884] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032885] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032934] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032935] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032983] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.032992] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.033060] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:50 vhs-4 kernel: [ 2630.033061] lost page write due to I/O error on md3
Feb 28 16:04:50 vhs-4 kernel: [ 2630.639998] EXT4-fs error: 56869 callbacks suppressed
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640003] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640005] EXT4-fs: 56869 callbacks suppressed
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640006] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640084] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640087] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640162] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640164] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640220] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640221] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640276] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640278] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640332] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640333] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640388] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640389] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640462] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640464] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640519] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640521] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640574] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:50 vhs-4 kernel: [ 2630.640576] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908293] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908298] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908321] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908343] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908364] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908386] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908407] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908428] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908449] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908470] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:55 vhs-4 kernel: [ 2634.908491] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:04:57 vhs-4 kernel: [ 2637.042488] EXT4-fs error: 87488 callbacks suppressed
Feb 28 16:04:57 vhs-4 kernel: [ 2637.042493] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.042496] EXT4-fs: 87488 callbacks suppressed
Feb 28 16:04:57 vhs-4 kernel: [ 2637.042497] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.106391] quiet_error: 99990 callbacks suppressed
Feb 28 16:04:57 vhs-4 kernel: [ 2637.106393] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.106395] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.106518] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.106521] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140375] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140377] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140516] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140518] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140530] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140533] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140593] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140595] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140601] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140603] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140650] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140652] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140657] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140658] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140705] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140706] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140712] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140713] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140759] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140760] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140765] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140766] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140811] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140812] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140818] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140819] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140864] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140865] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140871] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140872] lost page write due to I/O error on md3
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140916] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140918] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140923] Buffer I/O error on device md3, logical block 0
Feb 28 16:04:57 vhs-4 kernel: [ 2637.140924] lost page write due to I/O error on md3
Feb 28 16:05:01 vhs-4 CRON[20554]: (root) CMD (/opt/vht/bin/tv/tvUpdateLaunch.sh)
Feb 28 16:05:01 vhs-4 CRON[20555]: (root) CMD ( [ -x /opt/vht/bin/dns/dns-update-names.php ] && /opt/vht/bin/dns/dns-update-names.php && vlog "dns-update" "ok" || vlog "dns-update" "fail")
Feb 28 16:05:01 vhs-4 CRON[20556]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /opt/vht/wshserver/var/lib/php5 ] && find /opt/vht/wshserver/var/lib/php5 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm)
Feb 28 16:05:01 vhs-4 CRON[20563]: (root) CMD ( [ -x /opt/vht/appserver/app/users/bin/connectiontracker-persist.php ] && /opt/vht/appserver/app/users/bin/connectiontracker-persist.php)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113028] EXT4-fs error: 99691 callbacks suppressedHors ligne
#195 Le 21/03/2023, à 20:03
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Tu as eu un événement anormal.
SDC a eu un problème que j'espère identifier dans la trace que tu viens de fournir.
Par réparer, cela veut dire qu'il va remplacer le disque SDC par le disque SDB en utilisant les disques SDA et SDD
Je pense qu'à cause de cette table GPT mal située, il s'est planté....
Sinon il aurait réussi et t'aurait certainement dit de remplacer SDC en prévision d'autre autre panne.
Dernière modification par geole (Le 21/03/2023, à 22:42)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#196 Le 21/03/2023, à 20:11
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Suite
jm@jm-OptiPlex-9020:~$ tail -9000 /mnt/var/log/syslog.1 | head -1000
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113032] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113034] EXT4-fs: 99691 callbacks suppressed
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113036] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113114] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113115] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113188] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113189] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113262] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113264] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113333] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113334] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113403] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113405] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113460] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113461] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113517] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113518] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113573] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113575] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113629] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:02 vhs-4 kernel: [ 2642.113631] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129354] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129358] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129383] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129407] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129430] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129452] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129475] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129498] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129521] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129544] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:02 vhs-4 kernel: [ 2642.129566] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:03 vhs-4 kernel: [ 2643.257515] quiet_error: 99990 callbacks suppressed
Feb 28 16:05:03 vhs-4 kernel: [ 2643.257519] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:03 vhs-4 kernel: [ 2643.257521] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.536773] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.536777] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.536921] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.536924] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.536992] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.536994] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537066] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537069] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537190] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537191] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537245] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537247] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537326] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537328] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537379] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537380] lost page write due to I/O error on md3
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537432] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:04 vhs-4 kernel: [ 2644.537433] lost page write due to I/O error on md3
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122785] EXT4-fs error: 51924 callbacks suppressed
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122790] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122792] EXT4-fs: 51924 callbacks suppressed
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122793] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122849] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122850] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122903] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122904] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122958] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.122960] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123013] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123014] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123067] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123068] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123122] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123124] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123178] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123180] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123232] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123234] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123288] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:07 vhs-4 kernel: [ 2647.123289] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524525] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524530] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524553] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524575] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524596] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524618] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524639] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524660] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524682] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524703] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:09 vhs-4 kernel: [ 2649.524724] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:11 vhs-4 kernel: [ 2651.755837] quiet_error: 99991 callbacks suppressed
Feb 28 16:05:11 vhs-4 kernel: [ 2651.755841] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.755843] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790027] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790032] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790230] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790232] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790316] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790318] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790392] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790394] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790467] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790469] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790560] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790562] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790622] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790624] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790696] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790698] lost page write due to I/O error on md3
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790751] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:11 vhs-4 kernel: [ 2651.790752] lost page write due to I/O error on md3
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132488] EXT4-fs error: 55358 callbacks suppressed
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132492] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132494] EXT4-fs: 55358 callbacks suppressed
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132495] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132552] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132554] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132607] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132609] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132663] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132664] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132718] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132719] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132773] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132775] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132830] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132831] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132885] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132887] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132940] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132942] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132996] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:12 vhs-4 kernel: [ 2652.132998] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:13 vhs-4 kernel: [ 2653.629705] init: vht/mysql-sys main process (9498) terminated with status 1
Feb 28 16:05:13 vhs-4 kernel: [ 2653.629716] init: vht/mysql-sys main process ended, respawning
Feb 28 16:05:13 vhs-4 afpd[12079]: AFP Server shutting down on SIGTERM
Feb 28 16:05:13 vhs-4 kernel: [ 2653.639122] init: vsftpd main process (12739) killed by TERM signal
Feb 28 16:05:13 vhs-4 kernel: [ 2653.663273] init: smbd main process (12069) killed by TERM signal
Feb 28 15:27:02 vhs-4 console-kit-daemon[7897]: GLib-CRITICAL: Source ID 12 was not found when attempting to remove it
Feb 28 16:05:13 vhs-4 console-kit-daemon[7897]: GLib-CRITICAL: Source ID 33 was not found when attempting to remove it
Feb 28 16:05:13 vhs-4 rpc.mountd[12236]: Caught signal 15, un-registering and exiting.
Feb 28 16:05:13 vhs-4 kernel: [ 2653.710430] nfsd: last server has exited, flushing export cache
Feb 28 16:05:13 vhs-4 rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Feb 28 16:05:13 vhs-4 kernel: [ 2653.733838] init: rpcbind main process (12033) terminated with status 2
Feb 28 16:05:14 vhs-4 kernel: [ 2654.645389] init: vht/xbmc main process (13770) terminated with status 1
Feb 28 16:05:15 vhs-4 kernel: [ 2655.203485] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:15 vhs-4 kernel: [ 2655.203496] EXT4-fs warning (device md3): __ext4_read_dirblock:675: error reading directory block (ino 426246373, block 0)
Feb 28 16:05:15 vhs-4 kernel: [ 2655.206457] EXT4-fs warning (device md3): __ext4_read_dirblock:675: error reading directory block (ino 426246373, block 0)
Feb 28 16:05:15 vhs-4 kernel: [ 2655.206495] EXT4-fs warning (device md3): __ext4_read_dirblock:675: error reading directory block (ino 426246373, block 0)
Feb 28 16:05:15 vhs-4 postfix/sendmail[21013]: fatal: open /etc/postfix/main.cf: No such file or directory
Feb 28 16:05:15 vhs-4 CRON[20551]: (root) MAIL (mailed 1 byte of output; but got status 0x004b, #012)
Feb 28 16:05:16 vhs-4 kernel: [ 2655.957959] init: vht/mdgrabbers main process (12381) killed by ABRT signal
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797847] quiet_error: 98206 callbacks suppressed
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797850] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797852] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797904] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797905] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797958] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.797959] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798012] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798013] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798075] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798076] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798127] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798129] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798181] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798190] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798239] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798240] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798288] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798289] lost page write due to I/O error on md3
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798338] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:16 vhs-4 kernel: [ 2656.798339] lost page write due to I/O error on md3
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886391] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886418] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886442] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886465] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886488] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886511] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:17 vhs-4 kernel: [ 2656.886534] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:19 vhs-4 kernel: [ 2658.995553] EXT4-fs error: 92988 callbacks suppressed
Feb 28 16:05:19 vhs-4 kernel: [ 2658.995557] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2658.995560] EXT4-fs: 92988 callbacks suppressed
Feb 28 16:05:19 vhs-4 kernel: [ 2658.995562] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.070640] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.070643] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098202] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098204] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098276] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098278] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098341] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098342] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098406] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098407] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098471] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098473] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098523] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098524] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098581] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098582] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098632] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:19 vhs-4 kernel: [ 2659.098634] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:19 vhs-4 kernel: [ 2659.388020] init: vht/btsync main process (11997) killed by KILL signal
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807567] quiet_error: 56717 callbacks suppressed
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807571] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807572] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807625] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807626] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807678] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807679] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807731] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807732] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807783] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807784] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807836] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807837] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807888] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807889] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807940] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807941] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807992] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.807994] lost page write due to I/O error on md3
Feb 28 16:05:21 vhs-4 kernel: [ 2661.808046] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:21 vhs-4 kernel: [ 2661.808047] lost page write due to I/O error on md3
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062382] EXT4-fs warning: 99993 callbacks suppressed
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062386] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062412] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062435] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062457] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062480] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062503] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062526] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062548] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062571] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.062594] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:24 vhs-4 kernel: [ 2664.698479] init: vht/indexer main process (11242) killed by KILL signal
Feb 28 16:05:25 vhs-4 kernel: [ 2665.132741] init: vht/mysql-sys main process (21265) terminated with status 1
Feb 28 16:05:25 vhs-4 kernel: [ 2665.132754] init: vht/mysql-sys main process ended, respawning
Feb 28 16:05:26 vhs-4 kernel: [ 2666.231144] EXT4-fs error: 99991 callbacks suppressed
Feb 28 16:05:26 vhs-4 kernel: [ 2666.231149] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.231151] EXT4-fs: 99991 callbacks suppressed
Feb 28 16:05:26 vhs-4 kernel: [ 2666.231153] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.366296] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.366301] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395256] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395260] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395359] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395360] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395423] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395424] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395488] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395490] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395543] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395545] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395597] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395598] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395648] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395650] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395699] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:26 vhs-4 kernel: [ 2666.395700] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817273] quiet_error: 52983 callbacks suppressed
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817276] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817278] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817333] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817334] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817389] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817390] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817444] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817445] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817500] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817501] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817556] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817557] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817610] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817612] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817665] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817667] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817721] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817722] lost page write due to I/O error on md3
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817776] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:26 vhs-4 kernel: [ 2666.817777] lost page write due to I/O error on md3
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374491] EXT4-fs error: 96374 callbacks suppressed
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374496] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374498] EXT4-fs: 96374 callbacks suppressed
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374500] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374555] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374557] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374610] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374612] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374665] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374667] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374720] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374722] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374775] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374777] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374831] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374832] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374886] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374887] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374944] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.374946] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.375000] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:31 vhs-4 kernel: [ 2671.375001] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563036] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563040] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563063] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563085] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563106] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563128] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563149] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563170] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563191] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563212] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:31 vhs-4 kernel: [ 2671.563233] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:34 vhs-4 kernel: [ 2673.913587] quiet_error: 92054 callbacks suppressed
Feb 28 16:05:34 vhs-4 kernel: [ 2673.913590] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.913592] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.947986] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.947990] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948179] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948187] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948274] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948275] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948323] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948324] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948370] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948371] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948416] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948416] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948460] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948461] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948504] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948505] lost page write due to I/O error on md3
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948548] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:34 vhs-4 kernel: [ 2673.948548] lost page write due to I/O error on md3
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384210] EXT4-fs error: 51560 callbacks suppressed
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384214] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384216] EXT4-fs: 51560 callbacks suppressed
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384217] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384269] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384271] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384323] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384325] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384376] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384378] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384427] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384428] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384479] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384480] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384530] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384531] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384582] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384583] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384633] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384634] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384685] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:36 vhs-4 kernel: [ 2676.384686] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955157] quiet_error: 98994 callbacks suppressed
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955161] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955163] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955212] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955213] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955262] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955263] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955312] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955313] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955362] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955363] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955411] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955412] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955460] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955461] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955511] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955512] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955562] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955563] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955613] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:39 vhs-4 kernel: [ 2678.955614] lost page write due to I/O error on md3
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010549] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010553] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010578] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010602] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010625] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010648] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010671] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010694] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010716] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010739] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:39 vhs-4 kernel: [ 2679.010762] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:41 vhs-4 kernel: [ 2681.393908] EXT4-fs error: 54020 callbacks suppressed
Feb 28 16:05:41 vhs-4 kernel: [ 2681.393913] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.393914] EXT4-fs: 54020 callbacks suppressed
Feb 28 16:05:41 vhs-4 kernel: [ 2681.393916] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.393976] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.393977] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394028] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394029] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394079] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394081] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394131] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394132] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394183] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394185] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394235] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394236] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394287] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394288] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394339] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394340] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394390] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:41 vhs-4 kernel: [ 2681.394392] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964863] quiet_error: 52156 callbacks suppressed
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964867] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964869] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964923] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964924] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964976] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.964977] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965030] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965031] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965084] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965085] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965138] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965139] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965192] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965193] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965246] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965247] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965299] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965301] lost page write due to I/O error on md3
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965353] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:44 vhs-4 kernel: [ 2683.965354] lost page write due to I/O error on md3
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403661] EXT4-fs error: 96619 callbacks suppressed
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403665] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403667] EXT4-fs: 96619 callbacks suppressed
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403668] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403719] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403721] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403770] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403771] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403820] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403822] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403871] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403873] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403922] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403924] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403973] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.403975] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.404024] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.404026] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.404075] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.404076] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.404126] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:46 vhs-4 kernel: [ 2686.404127] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475540] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475544] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475569] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475592] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475615] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475638] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475661] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475684] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475850] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475876] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:46 vhs-4 kernel: [ 2686.475897] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974570] quiet_error: 51280 callbacks suppressed
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974574] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974576] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974634] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974635] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974683] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974684] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974735] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974736] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974786] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974787] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974837] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974838] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974887] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974888] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974938] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974939] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974988] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.974989] lost page write due to I/O error on md3
Feb 28 16:05:49 vhs-4 kernel: [ 2688.975039] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:49 vhs-4 kernel: [ 2688.975040] lost page write due to I/O error on md3
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413385] EXT4-fs error: 51195 callbacks suppressed
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413390] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413392] EXT4-fs: 51195 callbacks suppressed
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413393] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413449] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413450] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413504] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413506] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413559] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413561] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413614] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413616] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413669] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413671] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413724] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413726] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413780] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413781] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413835] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413836] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413889] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:51 vhs-4 kernel: [ 2691.413891] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961302] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961306] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961327] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961346] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961365] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961384] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961402] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961421] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961440] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961458] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:54 vhs-4 kernel: [ 2693.961477] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:05:56 vhs-4 kernel: [ 2696.338289] quiet_error: 97530 callbacks suppressed
Feb 28 16:05:56 vhs-4 kernel: [ 2696.338292] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.338294] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350637] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350641] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350809] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350810] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350866] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350867] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350922] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350923] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350971] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.350971] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351082] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351085] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351169] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351172] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351224] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351225] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351276] Buffer I/O error on device md3, logical block 0
Feb 28 16:05:56 vhs-4 kernel: [ 2696.351277] lost page write due to I/O error on md3
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423093] EXT4-fs error: 51574 callbacks suppressed
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423098] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423100] EXT4-fs: 51574 callbacks suppressed
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423102] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423156] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423158] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423211] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423212] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423267] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423269] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423323] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423325] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423401] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423402] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423456] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423458] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423529] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423530] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423585] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423586] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423641] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:05:56 vhs-4 kernel: [ 2696.423642] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 CRON[23519]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356757] quiet_error: 97937 callbacks suppressed
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356760] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356762] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356818] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356819] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356871] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356873] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356926] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356927] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356981] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.356982] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357036] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357037] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357089] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357090] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357144] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357145] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357197] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357198] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357251] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:01 vhs-4 kernel: [ 2701.357252] lost page write due to I/O error on md3
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432838] EXT4-fs error: 97809 callbacks suppressed
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432842] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432844] EXT4-fs: 97809 callbacks suppressed
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432846] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432900] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432902] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432955] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.432957] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433010] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433011] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433065] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433067] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433127] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433128] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433187] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433188] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433247] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433249] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433302] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433303] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433353] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:01 vhs-4 kernel: [ 2701.433354] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471339] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471343] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471368] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471391] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471414] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471437] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471460] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471483] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471505] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471528] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:01 vhs-4 kernel: [ 2701.471551] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366471] quiet_error: 52840 callbacks suppressed
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366474] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366477] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366531] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366532] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366584] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366585] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366639] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366640] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366693] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366694] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366746] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366747] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366799] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366800] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366853] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366854] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366908] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366910] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366963] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:06 vhs-4 kernel: [ 2706.366964] lost page write due to I/O error on md3
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442514] EXT4-fs: 53048 callbacks suppressed
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442517] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442652] EXT4-fs error: 53049 callbacks suppressed
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442654] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442656] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442722] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442723] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442791] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442793] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442862] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442863] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442933] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442935] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442992] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.442994] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443048] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443050] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443104] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443105] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443159] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443161] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:06 vhs-4 kernel: [ 2706.443214] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921669] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921673] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921696] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921718] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921739] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921761] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921782] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921803] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921824] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921845] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2708.921866] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:09 vhs-4 kernel: [ 2709.190937] init: vht/mysql-sys main process (24094) terminated with status 1
Feb 28 16:06:09 vhs-4 kernel: [ 2709.190946] init: vht/mysql-sys main process ended, respawning
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376212] quiet_error: 51327 callbacks suppressed
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376216] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376217] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376269] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376270] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376318] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376319] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376369] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376370] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376418] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376419] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376468] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376469] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376517] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376518] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376577] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376578] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376635] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376636] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376695] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:11 vhs-4 kernel: [ 2711.376696] lost page write due to I/O error on md3
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452281] EXT4-fs error: 51301 callbacks suppressed
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452286] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452288] EXT4-fs: 51302 callbacks suppressed
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452289] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452345] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452347] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452401] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452403] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452458] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452460] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452514] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452515] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452570] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452572] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452626] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452627] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452682] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452683] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452737] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452739] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452793] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:11 vhs-4 kernel: [ 2711.452795] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:16 vhs-4 kernel: [ 2716.385904] quiet_error: 96782 callbacks suppressed
Feb 28 16:06:16 vhs-4 kernel: [ 2716.385907] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.385909] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.385967] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.385968] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386012] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386013] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386055] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386056] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386100] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386100] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386144] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386145] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386188] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386188] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386232] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386233] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386276] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386277] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386319] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:16 vhs-4 kernel: [ 2716.386320] lost page write due to I/O error on md3
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440192] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440196] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440219] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440241] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440262] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440284] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440306] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440327] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440348] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440369] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:16 vhs-4 kernel: [ 2716.440390] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:18 vhs-4 kernel: [ 2718.753784] EXT4-fs error: 96399 callbacks suppressed
Feb 28 16:06:18 vhs-4 kernel: [ 2718.753796] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.753799] EXT4-fs: 96399 callbacks suppressed
Feb 28 16:06:18 vhs-4 kernel: [ 2718.753800] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.818734] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.818738] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853573] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853576] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853676] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853678] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853739] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853740] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853784] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853786] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853829] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853830] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853873] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853874] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853918] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853919] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853963] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:18 vhs-4 kernel: [ 2718.853964] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395649] quiet_error: 51357 callbacks suppressed
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395653] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395655] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395704] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395705] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395755] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395756] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395807] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395808] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395856] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395857] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395907] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395908] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395956] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.395957] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.396019] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.396020] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.396080] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.396081] lost page write due to I/O error on md3
Feb 28 16:06:21 vhs-4 kernel: [ 2721.396139] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:21 vhs-4 kernel: [ 2721.396140] lost page write due to I/O error on md3
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826426] EXT4-fs error: 97659 callbacks suppressed
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826431] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826433] EXT4-fs: 97659 callbacks suppressed
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826434] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826492] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826493] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826537] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826538] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826581] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826583] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826626] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826627] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826671] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826672] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826717] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826718] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826761] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826762] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826807] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826808] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826852] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:23 vhs-4 kernel: [ 2723.826853] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952393] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952397] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952422] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952445] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952467] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952491] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952513] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952536] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952558] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952581] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:24 vhs-4 kernel: [ 2723.952603] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405354] quiet_error: 51862 callbacks suppressed
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405358] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405360] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405415] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405416] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405470] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405471] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405525] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405526] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405580] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405581] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405635] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405636] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405690] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405691] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405744] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405746] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405799] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405800] lost page write due to I/O error on md3
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405854] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:26 vhs-4 kernel: [ 2726.405855] lost page write due to I/O error on md3
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836127] EXT4-fs error: 51353 callbacks suppressed
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836131] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836133] EXT4-fs: 51353 callbacks suppressed
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836134] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836204] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836206] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836260] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836261] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836316] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836317] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836371] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836372] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836427] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836429] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836482] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836483] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836538] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836540] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836593] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836594] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836647] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:28 vhs-4 kernel: [ 2728.836648] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415102] quiet_error: 95214 callbacks suppressed
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415106] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415108] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415157] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415158] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415207] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415208] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415256] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415257] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415306] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415307] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415357] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415358] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415407] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415408] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415458] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415459] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415509] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415510] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415560] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:31 vhs-4 kernel: [ 2731.415561] lost page write due to I/O error on md3
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553215] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553219] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553245] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553268] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553291] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553314] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553337] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553359] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553382] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553405] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:31 vhs-4 kernel: [ 2731.553428] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898173] EXT4-fs error: 50959 callbacks suppressed
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898178] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898181] EXT4-fs: 50959 callbacks suppressed
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898182] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898280] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898282] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898349] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898350] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898418] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898420] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898488] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898490] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898544] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898545] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898601] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898602] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898663] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898664] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898724] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898726] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898785] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:33 vhs-4 kernel: [ 2733.898786] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424793] quiet_error: 51106 callbacks suppressed
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424797] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424799] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424856] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424857] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424908] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424909] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424953] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424954] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424998] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.424999] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425043] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425043] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425086] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425087] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425131] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425132] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425175] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425176] lost page write due to I/O error on md3
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425219] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:36 vhs-4 kernel: [ 2736.425220] lost page write due to I/O error on md3
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907628] EXT4-fs error: 96469 callbacks suppressed
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907634] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907636] EXT4-fs: 96469 callbacks suppressed
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907637] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907694] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907695] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907750] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907752] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907805] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907807] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907861] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907863] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907918] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907919] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907973] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.907974] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.908029] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.908031] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.908089] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.908090] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:38 vhs-4 kernel: [ 2738.908141] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:38 vhs-4 kernel: [ 2738.908142] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090381] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090385] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090405] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090424] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090443] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090485] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090507] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090528] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090554] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090572] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:39 vhs-4 kernel: [ 2739.090591] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:41 vhs-4 kernel: [ 2741.462090] quiet_error: 51485 callbacks suppressed
Feb 28 16:06:41 vhs-4 kernel: [ 2741.462094] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.462096] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500736] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500740] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500863] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500864] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500918] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500919] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500970] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.500971] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501020] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501021] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501071] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501072] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501122] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501123] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501173] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501174] lost page write due to I/O error on md3
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501223] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:41 vhs-4 kernel: [ 2741.501224] lost page write due to I/O error on md3
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917340] EXT4-fs error: 51114 callbacks suppressed
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917345] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917347] EXT4-fs: 51114 callbacks suppressed
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917348] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917408] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917410] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917459] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917461] EXT4-fs (md3): previous I/O error to superblock detectedHors ligne
#197 Le 21/03/2023, à 20:16
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Voila l'incident qui montre bien qu'il va bosser avec seulement deux disques.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247817] end_request: I/O error, dev sdc, sector 119241832
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247821] md/raid:md3: Disk failure on sdc3, disabling device.
Feb 28 16:04:10 vhs-4 kernel: [ 2590.247821] md/raid:md3: Operation continuing on 2 devices.Pour un historique facile à fabriquer
grep "I/O error" /mnt/var/log/syslog.1Je ne sais pas trop comment tu as été prévenu de l'incident.
Feb 28 15:58:32 vhs-4 postfix/sendmail[9435]: fatal: open /etc/postfix/main.cf: No such file or directory
Feb 28 15:58:32 vhs-4 postfix/sendmail[9446]: fatal: open /etc/postfix/main.cf: No such file or directoryDernière modification par geole (Le 21/03/2023, à 22:40)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#198 Le 21/03/2023, à 20:34
- geole
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
Encore un dernier coup double pour avoir le second incident
tail -8000 /mnt/var/log/syslog.1 | head -2000Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#199 Le 21/03/2023, à 20:36
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
C'est le serveur qui m'a envoyé un mail
Hors ligne
#200 Le 21/03/2023, à 20:38
- Jm78
Re : [Resolu]Probleme d'acces fichiers sur Serveur Ve-Hotech Xtrem 3 RAID5
jm@jm-OptiPlex-9020:~$ tail -8000 /mnt/var/log/syslog.1 | head -2000
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917510] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917512] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917563] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917564] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917615] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917616] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917666] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917667] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917720] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917721] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917772] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917773] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917823] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:43 vhs-4 kernel: [ 2743.917824] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508320] quiet_error: 98464 callbacks suppressed
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508324] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508325] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508381] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508382] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508440] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508441] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508496] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508497] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508553] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508554] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508608] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508609] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508663] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508664] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508719] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508721] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508776] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508777] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508832] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:46 vhs-4 kernel: [ 2746.508834] lost page write due to I/O error on md3
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587535] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587539] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587563] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587584] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587605] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587627] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587648] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587669] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587690] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587711] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:46 vhs-4 kernel: [ 2746.587733] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:49 vhs-4 kernel: [ 2748.970471] EXT4-fs error: 52387 callbacks suppressed
Feb 28 16:06:49 vhs-4 kernel: [ 2748.970476] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.970479] EXT4-fs: 52387 callbacks suppressed
Feb 28 16:06:49 vhs-4 kernel: [ 2748.970480] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998195] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998199] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998318] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998319] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998394] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998395] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998470] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998471] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998562] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998563] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998606] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998607] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998651] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998652] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998695] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998697] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998740] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:49 vhs-4 kernel: [ 2748.998741] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518036] quiet_error: 49932 callbacks suppressed
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518040] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518042] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518091] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518092] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518160] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518161] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518211] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518212] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518262] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518264] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518314] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518315] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518364] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518365] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518414] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518415] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518465] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518466] lost page write due to I/O error on md3
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518571] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:51 vhs-4 kernel: [ 2751.518572] lost page write due to I/O error on md3
Feb 28 16:06:53 vhs-4 kernel: [ 2753.365389] init: vht/mysql-sys main process (26818) terminated with status 1
Feb 28 16:06:53 vhs-4 kernel: [ 2753.365402] init: vht/mysql-sys main process ended, respawning
Feb 28 16:06:54 vhs-4 kernel: [ 2754.004903] EXT4-fs error: 95389 callbacks suppressed
Feb 28 16:06:54 vhs-4 kernel: [ 2754.004908] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.004910] EXT4-fs: 95389 callbacks suppressed
Feb 28 16:06:54 vhs-4 kernel: [ 2754.004911] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.004963] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.004964] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005015] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005016] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005065] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005067] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005117] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005118] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005169] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005170] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005221] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005222] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005273] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005274] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005323] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005325] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005375] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:54 vhs-4 kernel: [ 2754.005377] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:54 vhs-4 kernel: [ 2754.239934] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:06:54 vhs-4 kernel: [ 2754.239938] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.239961] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.239982] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240011] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240034] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240057] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240086] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240107] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240129] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:54 vhs-4 kernel: [ 2754.240150] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:06:56 vhs-4 kernel: [ 2756.539657] quiet_error: 51575 callbacks suppressed
Feb 28 16:06:56 vhs-4 kernel: [ 2756.539660] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.539662] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.539857] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.539860] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540012] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540014] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540137] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540140] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540209] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540212] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540278] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540281] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540331] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540332] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540381] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540382] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540431] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540432] lost page write due to I/O error on md3
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540480] Buffer I/O error on device md3, logical block 0
Feb 28 16:06:56 vhs-4 kernel: [ 2756.540481] lost page write due to I/O error on md3
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014630] EXT4-fs error: 51469 callbacks suppressed
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014634] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014637] EXT4-fs: 51469 callbacks suppressed
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014638] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014695] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014697] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014752] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014753] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014807] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014808] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014862] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014863] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014918] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014920] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014973] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.014975] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.015028] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.015030] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.015083] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.015084] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:06:59 vhs-4 kernel: [ 2759.015146] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:06:59 vhs-4 kernel: [ 2759.015147] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549473] quiet_error: 96084 callbacks suppressed
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549477] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549479] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549535] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549538] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549592] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549594] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549647] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549648] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549702] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549703] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549757] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549758] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549812] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549813] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549866] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549867] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549921] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549922] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549975] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:01 vhs-4 kernel: [ 2761.549976] lost page write due to I/O error on md3
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754656] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754660] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754681] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754700] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754718] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754737] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754755] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754773] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754792] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754810] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:01 vhs-4 kernel: [ 2761.754828] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:04 vhs-4 kernel: [ 2764.112938] EXT4-fs error: 53112 callbacks suppressed
Feb 28 16:07:04 vhs-4 kernel: [ 2764.112943] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.112946] EXT4-fs: 53112 callbacks suppressed
Feb 28 16:07:04 vhs-4 kernel: [ 2764.112947] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148187] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148192] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148247] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148249] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148300] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148301] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148352] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148354] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148403] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148405] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148477] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148478] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148560] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148562] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148612] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148613] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148663] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:04 vhs-4 kernel: [ 2764.148664] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559249] quiet_error: 50956 callbacks suppressed
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559254] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559255] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559315] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559317] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559367] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559368] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559419] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559420] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559470] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559471] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559522] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559523] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559573] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559574] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559625] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559626] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559677] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559678] lost page write due to I/O error on md3
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559728] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:06 vhs-4 kernel: [ 2766.559729] lost page write due to I/O error on md3
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154175] EXT4-fs error: 97391 callbacks suppressed
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154180] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154183] EXT4-fs: 97391 callbacks suppressed
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154184] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154242] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154244] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154298] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154300] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154354] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154355] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154409] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154410] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154464] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154466] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154520] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154521] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154590] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154592] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154647] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154648] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154725] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:09 vhs-4 kernel: [ 2769.154726] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284801] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284806] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284829] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284851] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284872] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284894] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284915] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284936] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284957] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.284979] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:09 vhs-4 kernel: [ 2769.285000] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578563] quiet_error: 52930 callbacks suppressed
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578567] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578568] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578714] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578717] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578878] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.578881] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579006] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579009] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579078] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579079] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579133] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579134] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579183] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579184] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579234] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579235] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579285] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579286] lost page write due to I/O error on md3
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579336] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:11 vhs-4 kernel: [ 2771.579337] lost page write due to I/O error on md3
Feb 28 16:07:14 vhs-4 kernel: [ 2774.163963] EXT4-fs error: 52090 callbacks suppressed
Feb 28 16:07:14 vhs-4 kernel: [ 2774.163967] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.163969] EXT4-fs: 52090 callbacks suppressed
Feb 28 16:07:14 vhs-4 kernel: [ 2774.163970] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164023] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164024] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164075] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164076] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164127] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164128] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164178] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164179] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164230] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164232] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164282] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164283] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164333] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164335] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164385] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164387] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164437] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:14 vhs-4 kernel: [ 2774.164438] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586685] quiet_error: 95830 callbacks suppressed
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586689] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586691] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586749] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586750] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586799] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586800] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586851] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586852] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586902] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586903] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586954] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.586955] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587006] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587007] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587057] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587058] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587109] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587110] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587160] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:16 vhs-4 kernel: [ 2776.587161] lost page write due to I/O error on md3
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808542] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808546] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808572] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808594] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808617] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808640] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808662] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808696] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808718] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808740] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:16 vhs-4 kernel: [ 2776.808763] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173608] EXT4-fs error: 52027 callbacks suppressed
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173612] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173614] EXT4-fs: 52027 callbacks suppressed
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173615] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173670] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173672] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173725] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173727] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173780] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173781] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173835] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173837] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173891] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173893] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173947] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.173948] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.174001] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.174003] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.174058] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.174059] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:19 vhs-4 kernel: [ 2779.174113] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:19 vhs-4 kernel: [ 2779.174115] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596405] quiet_error: 52436 callbacks suppressed
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596416] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596418] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596469] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596470] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596520] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596521] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596571] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596572] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596621] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596622] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596672] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596673] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596723] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596724] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596780] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596781] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596825] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596825] lost page write due to I/O error on md3
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596870] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:21 vhs-4 kernel: [ 2781.596871] lost page write due to I/O error on md3
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183328] EXT4-fs error: 95949 callbacks suppressed
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183332] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183334] EXT4-fs: 95949 callbacks suppressed
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183335] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183389] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183390] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183441] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183443] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183492] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183493] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183542] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183543] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183594] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183595] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183646] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183647] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183698] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183699] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183748] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183749] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183799] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:24 vhs-4 kernel: [ 2784.183801] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314518] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314523] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314546] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314568] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314589] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314611] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314632] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314654] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314675] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314696] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:24 vhs-4 kernel: [ 2784.314718] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:26 vhs-4 kernel: [ 2786.623241] quiet_error: 51703 callbacks suppressed
Feb 28 16:07:26 vhs-4 kernel: [ 2786.623244] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.623246] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.650889] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.650895] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651046] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651048] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651162] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651163] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651248] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651249] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651304] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651305] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651358] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651359] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651409] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651410] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651459] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651460] lost page write due to I/O error on md3
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651509] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:26 vhs-4 kernel: [ 2786.651510] lost page write due to I/O error on md3
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193094] EXT4-fs error: 52220 callbacks suppressed
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193098] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193100] EXT4-fs: 52220 callbacks suppressed
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193102] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193157] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193158] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193217] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193218] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193268] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193269] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193320] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193321] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193370] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193372] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193422] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193424] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193473] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193474] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193524] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193526] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193575] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:29 vhs-4 kernel: [ 2789.193576] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:31 vhs-4 kernel: [ 2791.659904] quiet_error: 97946 callbacks suppressed
Feb 28 16:07:31 vhs-4 kernel: [ 2791.659907] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.659909] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.659964] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.659965] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660019] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660020] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660074] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660075] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660129] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660130] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660183] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660184] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660238] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660239] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660293] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660294] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660348] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660349] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660403] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:31 vhs-4 kernel: [ 2791.660404] lost page write due to I/O error on md3
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772769] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772773] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772799] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772822] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772845] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772868] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772891] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772914] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772936] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772959] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:31 vhs-4 kernel: [ 2791.772982] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202842] EXT4-fs error: 54022 callbacks suppressed
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202847] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202849] EXT4-fs: 54022 callbacks suppressed
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202850] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202906] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202908] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202967] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.202968] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203017] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203018] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203068] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203070] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203119] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203120] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203171] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203173] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203223] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203225] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203274] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203276] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203325] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:34 vhs-4 kernel: [ 2794.203326] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669624] quiet_error: 55300 callbacks suppressed
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669627] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669629] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669678] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669679] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669728] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669729] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669780] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669781] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669829] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669830] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669879] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669880] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669929] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669930] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669979] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.669980] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.670032] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.670033] lost page write due to I/O error on md3
Feb 28 16:07:36 vhs-4 kernel: [ 2796.670083] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:36 vhs-4 kernel: [ 2796.670084] lost page write due to I/O error on md3
Feb 28 16:07:37 vhs-4 kernel: [ 2797.395791] init: vht/mysql-sys main process (29637) terminated with status 1
Feb 28 16:07:37 vhs-4 kernel: [ 2797.395801] init: vht/mysql-sys main process ended, respawning
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061874] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061878] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061904] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061927] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061950] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061973] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.061996] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.062019] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.062041] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.062064] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:39 vhs-4 kernel: [ 2799.062087] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:41 vhs-4 kernel: [ 2801.192087] EXT4-fs error: 96230 callbacks suppressed
Feb 28 16:07:41 vhs-4 kernel: [ 2801.192092] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.192095] EXT4-fs: 96230 callbacks suppressed
Feb 28 16:07:41 vhs-4 kernel: [ 2801.192096] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.243855] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.243858] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.243916] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.243918] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.243969] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.243970] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244051] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244053] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244122] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244123] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244197] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244198] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244252] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244253] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244307] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244308] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244361] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:41 vhs-4 kernel: [ 2801.244362] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679360] quiet_error: 55286 callbacks suppressed
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679364] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679365] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679415] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679416] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679465] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679466] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679515] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679516] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679564] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679565] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679614] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679615] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679664] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679665] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679714] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679715] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679764] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679765] lost page write due to I/O error on md3
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679814] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:41 vhs-4 kernel: [ 2801.679815] lost page write due to I/O error on md3
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065195] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065199] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065222] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065243] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065264] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065286] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065307] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065328] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065348] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065369] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:46 vhs-4 kernel: [ 2806.065390] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:48 vhs-4 kernel: [ 2808.263739] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:07:48 vhs-4 kernel: [ 2808.263744] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.263747] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:07:48 vhs-4 kernel: [ 2808.263748] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340546] quiet_error: 91428 callbacks suppressed
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340550] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340552] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340677] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340681] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340706] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340709] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340773] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340775] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340782] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340785] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340847] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340849] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340857] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340860] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340925] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340927] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340934] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.340937] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341022] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341024] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341031] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341033] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341104] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341106] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341113] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341114] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341164] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341165] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341172] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341173] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341221] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341222] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341228] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341229] lost page write due to I/O error on md3
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341278] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341280] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341286] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:48 vhs-4 kernel: [ 2808.341287] lost page write due to I/O error on md3
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344479] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344483] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344504] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344523] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344541] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344560] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344579] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344597] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344624] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344660] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:53 vhs-4 kernel: [ 2813.344691] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:07:55 vhs-4 kernel: [ 2815.393584] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:07:55 vhs-4 kernel: [ 2815.393589] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.393592] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:07:55 vhs-4 kernel: [ 2815.393593] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485731] quiet_error: 99990 callbacks suppressed
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485735] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485737] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485854] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485857] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485867] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485869] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485920] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485921] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485927] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485929] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485976] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485978] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485986] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.485988] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486034] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486035] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486041] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486042] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486088] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486089] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486095] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486096] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486140] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486141] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486146] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486148] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486192] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486193] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486199] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486200] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486245] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486247] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486252] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486253] lost page write due to I/O error on md3
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486297] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486299] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486304] Buffer I/O error on device md3, logical block 0
Feb 28 16:07:55 vhs-4 kernel: [ 2815.486305] lost page write due to I/O error on md3
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452571] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452575] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452595] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452614] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452633] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452651] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452670] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452688] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452707] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452726] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:00 vhs-4 kernel: [ 2820.452754] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:01 vhs-4 CRON[31782]: (root) CMD (/opt/vht/bin/network/net-map.sh)
Feb 28 16:08:02 vhs-4 kernel: [ 2822.624884] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:08:02 vhs-4 kernel: [ 2822.624888] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.624891] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:08:02 vhs-4 kernel: [ 2822.624892] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678717] quiet_error: 99990 callbacks suppressed
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678721] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678722] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678840] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678843] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678853] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678856] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678909] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678910] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678917] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.678918] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683367] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683369] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683383] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683386] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683457] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683459] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683465] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683466] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683515] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683517] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683522] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683523] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683570] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683571] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683577] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683578] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683624] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683625] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683630] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683632] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683677] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683679] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683684] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683685] lost page write due to I/O error on md3
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683730] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683731] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683737] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:02 vhs-4 kernel: [ 2822.683738] lost page write due to I/O error on md3
Feb 28 16:08:07 vhs-4 kernel: [ 2827.526892] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:07 vhs-4 kernel: [ 2827.526896] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.526922] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.526946] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.526968] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.526992] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.527015] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.527038] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.527060] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.527083] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:07 vhs-4 kernel: [ 2827.527106] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:09 vhs-4 kernel: [ 2829.678392] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:08:09 vhs-4 kernel: [ 2829.678397] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.678400] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:08:09 vhs-4 kernel: [ 2829.678401] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726614] quiet_error: 99990 callbacks suppressed
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726617] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726618] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726740] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726743] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726759] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726761] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726809] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726811] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726817] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726818] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726863] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726865] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726870] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726872] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726918] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726919] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726924] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726926] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726989] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726992] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.726999] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727001] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727061] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727063] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727069] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727070] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727116] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727118] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727123] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727124] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727171] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727172] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727177] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727179] lost page write due to I/O error on md3
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727225] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727226] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727231] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:09 vhs-4 kernel: [ 2829.727232] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733179] EXT4-fs error: 99196 callbacks suppressed
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733183] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733185] EXT4-fs: 99196 callbacks suppressed
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733186] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733201] quiet_error: 99196 callbacks suppressed
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733204] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733206] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733252] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733254] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733260] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733261] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733310] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733311] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733316] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733317] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733358] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733359] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733364] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733365] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733404] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733405] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733410] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733411] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733451] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733453] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733457] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733458] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733497] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733498] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733503] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733504] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733543] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733545] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733549] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733550] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733591] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733592] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733597] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733598] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733637] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733638] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733643] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:14 vhs-4 kernel: [ 2834.733644] lost page write due to I/O error on md3
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768478] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768480] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768503] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768525] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768546] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768568] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768589] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768610] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768631] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768653] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:14 vhs-4 kernel: [ 2834.768674] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742827] EXT4-fs error: 59090 callbacks suppressed
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742831] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742833] EXT4-fs: 59090 callbacks suppressed
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742835] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742850] quiet_error: 59090 callbacks suppressed
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742853] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742854] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742900] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742902] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742914] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742916] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742955] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742956] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742961] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.742962] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743002] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743004] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743008] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743009] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743049] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743051] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743055] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743056] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743095] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743096] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743101] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743102] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743142] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743143] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743148] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743149] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743188] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743189] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743194] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743195] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743234] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743235] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743240] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743241] lost page write due to I/O error on md3
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743284] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743285] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743290] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:19 vhs-4 kernel: [ 2839.743291] lost page write due to I/O error on md3
Feb 28 16:08:21 vhs-4 kernel: [ 2841.386190] init: vht/mysql-sys main process (1053) terminated with status 1
Feb 28 16:08:21 vhs-4 kernel: [ 2841.386202] init: vht/mysql-sys main process ended, respawning
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881586] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881590] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881616] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881639] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881662] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881685] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881708] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881731] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881754] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881776] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:21 vhs-4 kernel: [ 2841.881799] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752576] EXT4-fs error: 55327 callbacks suppressed
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752581] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752583] EXT4-fs: 55327 callbacks suppressed
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752584] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752591] quiet_error: 55327 callbacks suppressed
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752594] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752595] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752641] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752643] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752648] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752649] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752695] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752696] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752702] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752703] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752748] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752749] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752755] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752756] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752801] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752802] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752807] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752809] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752853] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752855] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752860] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752861] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752906] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752907] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752912] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752914] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752958] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752960] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752965] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.752966] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753012] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753013] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753024] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753026] lost page write due to I/O error on md3
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753088] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753089] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753097] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:24 vhs-4 kernel: [ 2844.753099] lost page write due to I/O error on md3
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899208] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899212] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899240] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899261] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899282] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899303] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899324] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899345] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899366] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899387] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:28 vhs-4 kernel: [ 2848.899408] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:31 vhs-4 kernel: [ 2851.128337] EXT4-fs error: 86347 callbacks suppressed
Feb 28 16:08:31 vhs-4 kernel: [ 2851.128342] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.128345] EXT4-fs: 86347 callbacks suppressed
Feb 28 16:08:31 vhs-4 kernel: [ 2851.128346] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188455] quiet_error: 86347 callbacks suppressed
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188459] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188461] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188603] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188606] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188613] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188614] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188715] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188718] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188729] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188730] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188807] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188809] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188816] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188817] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188874] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188876] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188882] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188884] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188935] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188936] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188942] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188944] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188992] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188994] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.188999] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189000] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189048] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189050] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189056] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189057] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189104] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189106] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189112] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189113] lost page write due to I/O error on md3
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189161] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189162] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189168] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:31 vhs-4 kernel: [ 2851.189169] lost page write due to I/O error on md3
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112754] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112759] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112782] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112804] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112825] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112846] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112867] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112888] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112909] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112930] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:36 vhs-4 kernel: [ 2856.112951] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:38 vhs-4 kernel: [ 2858.144899] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:08:38 vhs-4 kernel: [ 2858.144904] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.144907] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:08:38 vhs-4 kernel: [ 2858.144908] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205256] quiet_error: 99990 callbacks suppressed
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205259] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205261] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205359] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205362] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205368] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205369] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205412] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205414] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205419] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205420] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205460] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205461] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205466] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205467] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205508] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205509] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205514] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205515] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205553] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205554] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205559] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205560] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205599] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205600] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205605] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205606] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205645] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205646] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205651] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205652] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205691] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205692] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205697] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205698] lost page write due to I/O error on md3
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205738] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205739] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205744] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:38 vhs-4 kernel: [ 2858.205745] lost page write due to I/O error on md3
Feb 28 16:08:43 vhs-4 kernel: [ 2863.155974] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:43 vhs-4 kernel: [ 2863.155978] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.156004] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.156027] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.156051] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.156077] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.156107] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.156965] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.157007] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.157034] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:43 vhs-4 kernel: [ 2863.157060] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:45 vhs-4 kernel: [ 2865.314443] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:08:45 vhs-4 kernel: [ 2865.314447] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.314450] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:08:45 vhs-4 kernel: [ 2865.314452] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368689] quiet_error: 99990 callbacks suppressed
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368693] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368695] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368828] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368832] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368840] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.368841] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369050] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369052] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369059] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369060] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369115] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369117] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369122] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369123] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369177] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369179] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369185] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369186] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369240] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369242] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369247] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369248] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369292] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369294] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369299] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369300] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369345] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369346] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369351] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369352] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369398] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369399] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369405] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369406] lost page write due to I/O error on md3
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369460] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369462] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369468] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:45 vhs-4 kernel: [ 2865.369469] lost page write due to I/O error on md3
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189385] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189389] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189413] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189434] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189456] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189477] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189499] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189520] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189541] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189571] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:50 vhs-4 kernel: [ 2870.189602] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:52 vhs-4 kernel: [ 2872.294431] EXT4-fs error: 99990 callbacks suppressed
Feb 28 16:08:52 vhs-4 kernel: [ 2872.294435] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.294438] EXT4-fs: 99990 callbacks suppressed
Feb 28 16:08:52 vhs-4 kernel: [ 2872.294439] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354106] quiet_error: 99990 callbacks suppressed
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354110] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354112] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354299] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354310] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354341] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354344] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354406] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354408] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354424] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354427] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354499] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354501] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354510] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354511] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354573] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354575] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354583] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354585] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354649] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354651] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354659] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354662] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354714] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354715] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354722] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354724] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354772] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354774] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354780] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354781] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354831] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354833] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354838] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354840] lost page write due to I/O error on md3
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354888] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354889] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354895] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:52 vhs-4 kernel: [ 2872.354896] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361786] EXT4-fs error: 98259 callbacks suppressed
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361790] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361793] EXT4-fs: 98259 callbacks suppressed
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361794] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361821] quiet_error: 98259 callbacks suppressed
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361824] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361825] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361877] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361879] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361884] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361885] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361925] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361926] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361931] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361932] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361971] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361973] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361977] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.361978] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362018] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362019] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362024] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362025] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362065] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362066] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362071] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362072] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362112] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362113] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362118] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362119] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362159] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362160] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362165] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362166] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362205] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362206] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362211] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362212] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362251] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362253] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362257] Buffer I/O error on device md3, logical block 0
Feb 28 16:08:57 vhs-4 kernel: [ 2877.362258] lost page write due to I/O error on md3
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437643] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437645] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437669] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437690] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437712] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437733] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437755] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437776] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437797] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437818] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:08:57 vhs-4 kernel: [ 2877.437840] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371500] EXT4-fs error: 60942 callbacks suppressed
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371504] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371506] EXT4-fs: 60942 callbacks suppressed
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371508] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371515] quiet_error: 60942 callbacks suppressed
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371518] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371519] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371569] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371571] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371584] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371586] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371631] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371632] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371638] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371639] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371684] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371686] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371691] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371692] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371738] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371740] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371745] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371746] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371791] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371793] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371798] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371799] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371845] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371846] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371852] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371853] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371899] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371900] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371906] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371907] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371951] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371953] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371958] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.371959] lost page write due to I/O error on md3
Feb 28 16:09:02 vhs-4 kernel: [ 2882.372004] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:02 vhs-4 kernel: [ 2882.372005] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:02 vhs-4 kernel: [ 2882.372011] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:02 vhs-4 kernel: [ 2882.372012] lost page write due to I/O error on md3
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404504] EXT4-fs warning: 99990 callbacks suppressed
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404508] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404532] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404554] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404575] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404597] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404618] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404639] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404661] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404682] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:04 vhs-4 kernel: [ 2884.404703] EXT4-fs warning (device md3): __ext4_read_dirblock:902: error reading directory block (ino 462422624, block 4)
Feb 28 16:09:05 vhs-4 kernel: [ 2885.228364] init: vht/mysql-sys main process (4441) terminated with status 1
Feb 28 16:09:05 vhs-4 kernel: [ 2885.228375] init: vht/mysql-sys main process ended, respawning
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381259] EXT4-fs error: 58353 callbacks suppressed
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381264] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381266] EXT4-fs: 58353 callbacks suppressed
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381267] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381274] quiet_error: 58353 callbacks suppressed
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381277] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381279] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381325] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381327] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381332] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381334] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381378] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381380] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381385] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381386] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381431] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381432] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381438] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381439] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381484] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381485] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381490] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381492] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381538] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381539] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381544] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381546] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381590] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381591] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381597] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381598] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381643] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381645] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381650] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381651] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381697] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381699] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381704] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381705] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381750] EXT4-fs error (device md3): __ext4_get_inode_loc:3932: inode #462423176: block 1849688168: comm du: unable to read itable block
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381751] EXT4-fs (md3): previous I/O error to superblock detected
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381757] Buffer I/O error on device md3, logical block 0
Feb 28 16:09:07 vhs-4 kernel: [ 2887.381758] lost page write due to I/O error on md3
Feb 28 16:09:07 vhs-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="948" x-info="http://www.rsyslog.com"] exiting on signal 15.
Feb 28 16:10:27 vhs-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="671" x-info="http://www.rsyslog.com"] start
Feb 28 16:10:27 vhs-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Feb 28 16:10:27 vhs-4 rsyslogd-2307: message repeated 2 times: [warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]]
Feb 28 16:10:27 vhs-4 rsyslogd: rsyslogd's groupid changed to 104
Feb 28 16:10:27 vhs-4 rsyslogd: rsyslogd's userid changed to 101
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Initializing cgroup subsys cpu
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Linux version 3.16.0-31-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 (Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Command line: root=/dev/md0 ro quiet splash vboot=key apparmor=0
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] KERNEL supported cpus:
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Intel GenuineIntel
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] AMD AuthenticAMD
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Centaur CentaurHauls
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000040200000-0x00000000b6d6dfff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6d6e000-0x00000000b6db6fff] ACPI NVS
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6db7000-0x00000000b6dbdfff] ACPI data
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6dbe000-0x00000000b6df4fff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6df5000-0x00000000b6df6fff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6df7000-0x00000000b6e07fff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6e08000-0x00000000b6e15fff] ACPI NVS
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6e16000-0x00000000b6e3cfff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6e3d000-0x00000000b6e7ffff] ACPI NVS
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b6e80000-0x00000000b6ffffff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000b7800000-0x00000000bf9fffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004405fffff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] NX (Execute Disable) protection: active
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] SMBIOS 2.7 present.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMI: Ve-hotech vhs-4xtreme/MINIX H61M-USB3, BIOS 4.6.4 02/18/2012
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] AGP: No AGP bridge found
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: last_pfn = 0x440600 max_arch_pfn = 0x400000000
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] MTRR default type: uncachable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] MTRR fixed ranges enabled:
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 00000-9FFFF write-back
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] A0000-BFFFF uncachable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] C0000-CFFFF write-protect
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] D0000-E7FFF uncachable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] E8000-FFFFF write-protect
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] MTRR variable ranges enabled:
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 0 base 000000000 mask C00000000 write-back
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 1 base 400000000 mask FC0000000 write-back
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 2 base 440000000 mask FFFC00000 write-back
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 3 base 440400000 mask FFFE00000 write-back
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 4 base 0B7800000 mask FFF800000 uncachable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 5 base 0B8000000 mask FF8000000 uncachable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 6 base 0C0000000 mask FC0000000 uncachable
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 7 disabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 8 disabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] 9 disabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] original variable MTRRs
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 0, base: 0GB, range: 16GB, type WB
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 1, base: 16GB, range: 1GB, type WB
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 2, base: 17GB, range: 4MB, type WB
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 3, base: 17412MB, range: 2MB, type WB
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 4, base: 2936MB, range: 8MB, type UC
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 5, base: 2944MB, range: 128MB, type UC
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reg 6, base: 3GB, range: 1GB, type UC
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] total RAM covered: 16254M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 64K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 128K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 256K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 512K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 1M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 2M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64K chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 16M num_reg: 10 lose cover RAM: -8M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -24M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 64M num_reg: 10 lose cover RAM: -56M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 128M num_reg: 10 lose cover RAM: -120M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 256M num_reg: 10 lose cover RAM: -240M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 512M num_reg: 10 lose cover RAM: -496M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 1G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 64K chunk_size: 2G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 128K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 512K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 1M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 2M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128K chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 16M num_reg: 10 lose cover RAM: -8M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 32M num_reg: 10 lose cover RAM: -24M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 64M num_reg: 10 lose cover RAM: -56M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 128M num_reg: 10 lose cover RAM: -120M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 256M num_reg: 10 lose cover RAM: -240M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 512M num_reg: 10 lose cover RAM: -496M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 1G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 128K chunk_size: 2G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256K chunk_size: 256K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256K chunk_size: 512K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256K chunk_size: 1M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256K chunk_size: 2M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256K chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256K chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 16M num_reg: 10 lose cover RAM: -8M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 32M num_reg: 10 lose cover RAM: -24M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 64M num_reg: 10 lose cover RAM: -56M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 128M num_reg: 10 lose cover RAM: -120M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 256M num_reg: 10 lose cover RAM: -240M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 512M num_reg: 10 lose cover RAM: -496M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 1G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 256K chunk_size: 2G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512K chunk_size: 512K num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512K chunk_size: 1M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512K chunk_size: 2M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512K chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512K chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 16M num_reg: 10 lose cover RAM: -8M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 32M num_reg: 10 lose cover RAM: -24M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 64M num_reg: 10 lose cover RAM: -56M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 128M num_reg: 10 lose cover RAM: -120M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 256M num_reg: 10 lose cover RAM: -240M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 512M num_reg: 10 lose cover RAM: -496M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 1G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 512K chunk_size: 2G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 1M chunk_size: 1M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 1M chunk_size: 2M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 1M chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 1M chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 16M num_reg: 10 lose cover RAM: -8M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 32M num_reg: 10 lose cover RAM: -24M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 64M num_reg: 10 lose cover RAM: -56M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 128M num_reg: 10 lose cover RAM: -120M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 256M num_reg: 10 lose cover RAM: -240M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 512M num_reg: 10 lose cover RAM: -496M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 1G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 1M chunk_size: 2G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 2M chunk_size: 2M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 2M chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 2M chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 16M num_reg: 10 lose cover RAM: -8M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 32M num_reg: 10 lose cover RAM: -24M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 64M num_reg: 10 lose cover RAM: -56M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 128M num_reg: 10 lose cover RAM: -120M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 256M num_reg: 10 lose cover RAM: -240M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 512M num_reg: 10 lose cover RAM: -496M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 1G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 2M chunk_size: 2G num_reg: 10 lose cover RAM: -992M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 4M chunk_size: 4M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 4M chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 16M num_reg: 10 lose cover RAM: -6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 32M num_reg: 10 lose cover RAM: -22M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 64M num_reg: 10 lose cover RAM: -54M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 128M num_reg: 10 lose cover RAM: -118M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 256M num_reg: 10 lose cover RAM: -238M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 512M num_reg: 10 lose cover RAM: -494M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 1G num_reg: 10 lose cover RAM: -990M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] *BAD*gran_size: 4M chunk_size: 2G num_reg: 10 lose cover RAM: -990M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 8M num_reg: 10 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 16M num_reg: 8 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 32M num_reg: 8 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 64M num_reg: 8 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 128M num_reg: 8 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 256M num_reg: 7 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 512M num_reg: 7 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 1G num_reg: 7 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 8M chunk_size: 2G num_reg: 8 lose cover RAM: 6M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 16M num_reg: 9 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 32M num_reg: 8 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 64M num_reg: 8 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 128M num_reg: 8 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 256M num_reg: 7 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 512M num_reg: 7 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 1G num_reg: 7 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 16M chunk_size: 2G num_reg: 8 lose cover RAM: 14M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 32M num_reg: 8 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 64M num_reg: 8 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 128M num_reg: 8 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 256M num_reg: 7 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 512M num_reg: 7 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 1G num_reg: 7 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 32M chunk_size: 2G num_reg: 8 lose cover RAM: 30M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64M chunk_size: 64M num_reg: 7 lose cover RAM: 62M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64M chunk_size: 128M num_reg: 8 lose cover RAM: 62M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64M chunk_size: 256M num_reg: 7 lose cover RAM: 62M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64M chunk_size: 512M num_reg: 7 lose cover RAM: 62M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64M chunk_size: 1G num_reg: 7 lose cover RAM: 62M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 64M chunk_size: 2G num_reg: 8 lose cover RAM: 62M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128M chunk_size: 128M num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128M chunk_size: 256M num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128M chunk_size: 512M num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128M chunk_size: 1G num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 128M chunk_size: 2G num_reg: 7 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256M chunk_size: 256M num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256M chunk_size: 512M num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256M chunk_size: 1G num_reg: 6 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 256M chunk_size: 2G num_reg: 7 lose cover RAM: 126M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512M chunk_size: 512M num_reg: 5 lose cover RAM: 382M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512M chunk_size: 1G num_reg: 6 lose cover RAM: 382M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 512M chunk_size: 2G num_reg: 7 lose cover RAM: 382M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 1G chunk_size: 1G num_reg: 4 lose cover RAM: 894M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 1G chunk_size: 2G num_reg: 5 lose cover RAM: 894M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] gran_size: 2G chunk_size: 2G num_reg: 3 lose cover RAM: 1918M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] mtrr_cleanup: can not find optimal value
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] please specify mtrr_gran_size/mtrr_chunk_size
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: update [mem 0xb7800000-0xffffffff] usable ==> reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: last_pfn = 0xb7000 max_arch_pfn = 0x400000000
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] found SMP MP-table at [mem 0x000fcea0-0x000fceaf] mapped at [ffff8800000fcea0]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Scanning 1 areas for low memory corruption
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] reserving inaccessible SNB gfx pages
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x00000000-0x000fffff] page 4k
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BRK [0x01fbe000, 0x01fbefff] PGTABLE
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BRK [0x01fbf000, 0x01fbffff] PGTABLE
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BRK [0x01fc0000, 0x01fc0fff] PGTABLE
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x440400000-0x4405fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x440400000-0x4405fffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BRK [0x01fc1000, 0x01fc1fff] PGTABLE
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x440000000-0x4403fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x440000000-0x4403fffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x400000000-0x43fffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x400000000-0x43fffffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BRK [0x01fc2000, 0x01fc2fff] PGTABLE
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x00100000-0x1fffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x00100000-0x001fffff] page 4k
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x00200000-0x1fffffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x20200000-0x3fffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x20200000-0x3fffffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x40200000-0xb6d6dfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x40200000-0xb6bfffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0xb6c00000-0xb6d6dfff] page 4k
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] BRK [0x01fc3000, 0x01fc3fff] PGTABLE
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0xb6df5000-0xb6df6fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0xb6df5000-0xb6df6fff] page 4k
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0xb6e80000-0xb6ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0xb6e80000-0xb6ffffff] page 4k
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] init_memory_mapping: [mem 0x100000000-0x3ffffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [mem 0x100000000-0x3ffffffff] page 2M
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] RAMDISK: [mem 0x1e309000-0x1ffeffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: Early table checksum verification disabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: RSDP 0x00000000000F0450 000024 (v02 ALASKA)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: XSDT 0x00000000B6DB7068 000054 (v01 ALASKA A M I 01072009 AMI 00010013)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: FACP 0x00000000B6DBDB60 0000F4 (v04 ALASKA A M I 01072009 AMI 00010013)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: DSDT 0x00000000B6DB7150 006A10 (v02 ALASKA A M I 00000570 INTL 20051117)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: FACS 0x00000000B6E0DF80 000040
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: APIC 0x00000000B6DBDC58 000072 (v03 ALASKA A M I 01072009 AMI 00010013)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: SSDT 0x00000000B6DBDCD0 000102 (v01 AMICPU PROC 00000001 MSFT 03000001)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: MCFG 0x00000000B6DBDDD8 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: HPET 0x00000000B6DBDE18 000038 (v01 ALASKA A M I 01072009 AMI. 00000004)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: ASPT 0x00000000B6DBDE50 000034 (v07 ALASKA PerfTune 01072009 AMI 00000000)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] No NUMA configuration found
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Faking a node at [mem 0x0000000000000000-0x00000004405fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x4405fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] NODE_DATA [mem 0x4405ec000-0x4405f0fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] [ffffea0000000000-ffffea00111fffff] PMD -> [ffff88042fc00000-ffff88043fbfffff] on node 0
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Zone ranges:
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA [mem 0x00001000-0x00ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Normal [mem 0x100000000-0x4405fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Movable zone start for each node
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Early memory node ranges
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0x00001000-0x0009cfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0x00100000-0x1fffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0x20200000-0x3fffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0x40200000-0xb6d6dfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0xb6df5000-0xb6df6fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0xb6e80000-0xb6ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] node 0: [mem 0x100000000-0x4405fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] On node 0 totalpages: 4157580
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA zone: 64 pages used for memmap
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA zone: 156 pages reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA zone: 3996 pages, LIFO batch:0
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA32 zone: 11628 pages used for memmap
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] DMA32 zone: 744176 pages, LIFO batch:31
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Normal zone: 53272 pages used for memmap
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Normal zone: 3409408 pages, LIFO batch:31
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Reserving Intel graphics stolen memory at 0xb7a00000-0xbf9fffff
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x408
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: IRQ0 used by override.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: IRQ2 used by override.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: IRQ9 used by override.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration information
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] nr_irqs_gsi: 40
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6d6e000-0xb6db6fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6db7000-0xb6dbdfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6dbe000-0xb6df4fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6df7000-0xb6e07fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6e08000-0xb6e15fff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6e16000-0xb6e3cfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb6e3d000-0xb6e7ffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb7000000-0xb77fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xb7800000-0xbf9fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xbfa00000-0xfed1bfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] e820: [mem 0xbfa00000-0xfed1bfff] available for PCI devices
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Booting paravirtualized kernel on bare hardware
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:4 nr_node_ids:1
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff880440200000 s82304 r8192 d24192 u524288
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] pcpu-alloc: s82304 r8192 d24192 u524288 alloc=1*2097152
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] pcpu-alloc: [0] 0 1 2 3
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4092460
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Policy zone: Normal
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Kernel command line: root=/dev/md0 ro quiet splash vboot=key apparmor=0
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] AGP: Checking aperture...
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] AGP: No AGP bridge found
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Memory: 16254976K/16630320K available (7617K kernel code, 1131K rwdata, 3596K rodata, 1356K init, 1300K bss, 375344K reserved)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Hierarchical RCU implementation.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Offload RCU callbacks from all CPUs
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Offload RCU callbacks from CPUs: 0-3.
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] NR_IRQS:16640 nr_irqs:712 16
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] Console: colour VGA+ 80x25
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] console [tty0] enabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] allocated 67108864 bytes of page_cgroup
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] hpet clockevent registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] tsc: Fast TSC calibration using PIT
Feb 28 16:10:27 vhs-4 kernel: [ 0.000000] tsc: Detected 2494.153 MHz processor
Feb 28 16:10:27 vhs-4 kernel: [ 0.000033] Calibrating delay loop (skipped), value calculated using timer frequency.. 4988.30 BogoMIPS (lpj=9976612)
Feb 28 16:10:27 vhs-4 kernel: [ 0.000036] pid_max: default: 32768 minimum: 301
Feb 28 16:10:27 vhs-4 kernel: [ 0.000042] ACPI: Core revision 20140424
Feb 28 16:10:27 vhs-4 kernel: [ 0.003541] ACPI: All ACPI Tables successfully acquired
Feb 28 16:10:27 vhs-4 kernel: [ 0.013324] Security Framework initialized
Feb 28 16:10:27 vhs-4 kernel: [ 0.013331] AppArmor: AppArmor disabled by boot time parameter
Feb 28 16:10:27 vhs-4 kernel: [ 0.013332] Yama: becoming mindful.
Feb 28 16:10:27 vhs-4 kernel: [ 0.014339] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.017517] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.018878] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.018896] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.019136] Initializing cgroup subsys memory
Feb 28 16:10:27 vhs-4 kernel: [ 0.019158] Initializing cgroup subsys devices
Feb 28 16:10:27 vhs-4 kernel: [ 0.019163] Initializing cgroup subsys freezer
Feb 28 16:10:27 vhs-4 kernel: [ 0.019166] Initializing cgroup subsys net_cls
Feb 28 16:10:27 vhs-4 kernel: [ 0.019170] Initializing cgroup subsys blkio
Feb 28 16:10:27 vhs-4 kernel: [ 0.019173] Initializing cgroup subsys perf_event
Feb 28 16:10:27 vhs-4 kernel: [ 0.019175] Initializing cgroup subsys net_prio
Feb 28 16:10:27 vhs-4 kernel: [ 0.019180] Initializing cgroup subsys hugetlb
Feb 28 16:10:27 vhs-4 kernel: [ 0.019201] CPU: Physical Processor ID: 0
Feb 28 16:10:27 vhs-4 kernel: [ 0.019202] CPU: Processor Core ID: 0
Feb 28 16:10:27 vhs-4 kernel: [ 0.019207] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Feb 28 16:10:27 vhs-4 kernel: [ 0.019207] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Feb 28 16:10:27 vhs-4 kernel: [ 0.019209] mce: CPU supports 9 MCE banks
Feb 28 16:10:27 vhs-4 kernel: [ 0.019222] CPU0: Thermal monitoring enabled (TM1)
Feb 28 16:10:27 vhs-4 kernel: [ 0.019231] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
Feb 28 16:10:27 vhs-4 kernel: [ 0.019231] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
Feb 28 16:10:27 vhs-4 kernel: [ 0.019231] tlb_flushall_shift: 6
Feb 28 16:10:27 vhs-4 kernel: [ 0.019347] Freeing SMP alternatives memory: 32K (ffffffff81e6f000 - ffffffff81e77000)
Feb 28 16:10:27 vhs-4 kernel: [ 0.020718] ftrace: allocating 29221 entries in 115 pages
Feb 28 16:10:27 vhs-4 kernel: [ 0.035010] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Feb 28 16:10:27 vhs-4 kernel: [ 0.074737] smpboot: CPU0: Intel(R) Core(TM) i5-2405S CPU @ 2.50GHz (fam: 06, model: 2a, stepping: 07)
Feb 28 16:10:27 vhs-4 kernel: [ 0.074745] TSC deadline timer enabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.074767] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
Feb 28 16:10:27 vhs-4 kernel: [ 0.074786] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
Feb 28 16:10:27 vhs-4 kernel: [ 0.074788] ... version: 3
Feb 28 16:10:27 vhs-4 kernel: [ 0.074789] ... bit width: 48
Feb 28 16:10:27 vhs-4 kernel: [ 0.074790] ... generic registers: 8
Feb 28 16:10:27 vhs-4 kernel: [ 0.074791] ... value mask: 0000ffffffffffff
Feb 28 16:10:27 vhs-4 kernel: [ 0.074792] ... max period: 0000ffffffffffff
Feb 28 16:10:27 vhs-4 kernel: [ 0.074793] ... fixed-purpose events: 3
Feb 28 16:10:27 vhs-4 kernel: [ 0.074793] ... event mask: 00000007000000ff
Feb 28 16:10:27 vhs-4 kernel: [ 0.076411] x86: Booting SMP configuration:
Feb 28 16:10:27 vhs-4 kernel: [ 0.076413] .... node #0, CPUs: #1
Feb 28 16:10:27 vhs-4 kernel: [ 0.089514] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Feb 28 16:10:27 vhs-4 kernel: [ 0.089596] #2 #3
Feb 28 16:10:27 vhs-4 kernel: [ 0.115792] x86: Booted up 1 node, 4 CPUs
Feb 28 16:10:27 vhs-4 kernel: [ 0.115795] smpboot: Total of 4 processors activated (19953.22 BogoMIPS)
Feb 28 16:10:27 vhs-4 kernel: [ 0.118836] devtmpfs: initialized
Feb 28 16:10:27 vhs-4 kernel: [ 0.122356] evm: security.selinux
Feb 28 16:10:27 vhs-4 kernel: [ 0.122357] evm: security.SMACK64
Feb 28 16:10:27 vhs-4 kernel: [ 0.122358] evm: security.SMACK64EXEC
Feb 28 16:10:27 vhs-4 kernel: [ 0.122359] evm: security.SMACK64TRANSMUTE
Feb 28 16:10:27 vhs-4 kernel: [ 0.122360] evm: security.SMACK64MMAP
Feb 28 16:10:27 vhs-4 kernel: [ 0.122361] evm: security.ima
Feb 28 16:10:27 vhs-4 kernel: [ 0.122362] evm: security.capability
Feb 28 16:10:27 vhs-4 kernel: [ 0.122411] PM: Registering ACPI NVS region [mem 0xb6d6e000-0xb6db6fff] (299008 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.122416] PM: Registering ACPI NVS region [mem 0xb6e08000-0xb6e15fff] (57344 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.122420] PM: Registering ACPI NVS region [mem 0xb6e3d000-0xb6e7ffff] (274432 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.123280] pinctrl core: initialized pinctrl subsystem
Feb 28 16:10:27 vhs-4 kernel: [ 0.123350] regulator-dummy: no parameters
Feb 28 16:10:27 vhs-4 kernel: [ 0.123384] RTC time: 15:10:11, date: 02/28/23
Feb 28 16:10:27 vhs-4 kernel: [ 0.123431] NET: Registered protocol family 16
Feb 28 16:10:27 vhs-4 kernel: [ 0.123575] cpuidle: using governor ladder
Feb 28 16:10:27 vhs-4 kernel: [ 0.123578] cpuidle: using governor menu
Feb 28 16:10:27 vhs-4 kernel: [ 0.123625] ACPI: bus type PCI registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.123627] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Feb 28 16:10:27 vhs-4 kernel: [ 0.123695] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Feb 28 16:10:27 vhs-4 kernel: [ 0.123697] PCI: not using MMCONFIG
Feb 28 16:10:27 vhs-4 kernel: [ 0.123698] PCI: Using configuration type 1 for base access
Feb 28 16:10:27 vhs-4 kernel: [ 0.128199] ACPI: Added _OSI(Module Device)
Feb 28 16:10:27 vhs-4 kernel: [ 0.128201] ACPI: Added _OSI(Processor Device)
Feb 28 16:10:27 vhs-4 kernel: [ 0.128202] ACPI: Added _OSI(3.0 _SCP Extensions)
Feb 28 16:10:27 vhs-4 kernel: [ 0.128203] ACPI: Added _OSI(Processor Aggregator Device)
Feb 28 16:10:27 vhs-4 kernel: [ 0.129863] ACPI: Executed 1 blocks of module-level executable AML code
Feb 28 16:10:27 vhs-4 kernel: [ 0.131811] ACPI: Dynamic OEM Table Load:
Feb 28 16:10:27 vhs-4 kernel: [ 0.131817] ACPI: SSDT 0xFFFF880429958C00 0003E0 (v01 AMI IST 00000001 MSFT 03000001)
Feb 28 16:10:27 vhs-4 kernel: [ 0.132113] ACPI: Dynamic OEM Table Load:
Feb 28 16:10:27 vhs-4 kernel: [ 0.132117] ACPI: SSDT 0xFFFF8804298E8C00 0000E4 (v01 AMI CST 00000001 MSFT 03000001)
Feb 28 16:10:27 vhs-4 kernel: [ 0.132708] ACPI: Interpreter enabled
Feb 28 16:10:27 vhs-4 kernel: [ 0.132712] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580)
Feb 28 16:10:27 vhs-4 kernel: [ 0.132715] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580)
Feb 28 16:10:27 vhs-4 kernel: [ 0.132726] ACPI: (supports S0 S3 S4 S5)
Feb 28 16:10:27 vhs-4 kernel: [ 0.132727] ACPI: Using IOAPIC for interrupt routing
Feb 28 16:10:27 vhs-4 kernel: [ 0.132743] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Feb 28 16:10:27 vhs-4 kernel: [ 0.132789] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
Feb 28 16:10:27 vhs-4 kernel: [ 0.133092] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Feb 28 16:10:27 vhs-4 kernel: [ 0.133303] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Feb 28 16:10:27 vhs-4 kernel: [ 0.137019] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Feb 28 16:10:27 vhs-4 kernel: [ 0.137024] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137180] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137489] PCI host bridge to bus 0000:00
Feb 28 16:10:27 vhs-4 kernel: [ 0.137492] pci_bus 0000:00: root bus resource [bus 00-ff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137494] pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137495] pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137497] pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137499] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137500] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137502] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137503] pci_bus 0000:00: root bus resource [mem 0xbfa00000-0xffffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137511] pci 0000:00:00.0: [8086:0100] type 00 class 0x060000
Feb 28 16:10:27 vhs-4 kernel: [ 0.137590] pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.137621] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.137652] pci 0000:00:01.0: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.137693] pci 0000:00:02.0: [8086:0112] type 00 class 0x030000
Feb 28 16:10:27 vhs-4 kernel: [ 0.137703] pci 0000:00:02.0: reg 0x10: [mem 0xfb400000-0xfb7fffff 64bit]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137709] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137713] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137815] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
Feb 28 16:10:27 vhs-4 kernel: [ 0.137837] pci 0000:00:1a.0: reg 0x10: [mem 0xfbc03000-0xfbc033ff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.137927] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.137965] pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138005] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.138088] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.138126] pci 0000:00:1c.0: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138165] pci 0000:00:1c.1: [8086:1c12] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.138247] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.138286] pci 0000:00:1c.1: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138324] pci 0000:00:1c.2: [8086:1c14] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.138406] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.138444] pci 0000:00:1c.2: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138484] pci 0000:00:1c.3: [8086:1c16] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.138566] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.138605] pci 0000:00:1c.3: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138643] pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.138725] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.138763] pci 0000:00:1c.4: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138802] pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
Feb 28 16:10:27 vhs-4 kernel: [ 0.138883] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.138921] pci 0000:00:1c.5: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.138967] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
Feb 28 16:10:27 vhs-4 kernel: [ 0.138989] pci 0000:00:1d.0: reg 0x10: [mem 0xfbc02000-0xfbc023ff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139081] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.139117] pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 28 16:10:27 vhs-4 kernel: [ 0.139157] pci 0000:00:1f.0: [8086:1c5c] type 00 class 0x060100
Feb 28 16:10:27 vhs-4 kernel: [ 0.139325] pci 0000:00:1f.2: [8086:1c02] type 00 class 0x010601
Feb 28 16:10:27 vhs-4 kernel: [ 0.139344] pci 0000:00:1f.2: reg 0x10: [io 0xf0b0-0xf0b7]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139352] pci 0000:00:1f.2: reg 0x14: [io 0xf0a0-0xf0a3]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139360] pci 0000:00:1f.2: reg 0x18: [io 0xf090-0xf097]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139368] pci 0000:00:1f.2: reg 0x1c: [io 0xf080-0xf083]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139377] pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139385] pci 0000:00:1f.2: reg 0x24: [mem 0xfbc01000-0xfbc017ff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139430] pci 0000:00:1f.2: PME# supported from D3hot
Feb 28 16:10:27 vhs-4 kernel: [ 0.139496] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
Feb 28 16:10:27 vhs-4 kernel: [ 0.139514] pci 0000:00:1f.3: reg 0x10: [mem 0xfbc00000-0xfbc000ff 64bit]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139535] pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139648] pci 0000:01:00.0: [1131:7160] type 00 class 0x048000
Feb 28 16:10:27 vhs-4 kernel: [ 0.139670] pci 0000:01:00.0: reg 0x10: [mem 0xfbb00000-0xfbbfffff 64bit]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139768] pci 0000:01:00.0: supports D1 D2
Feb 28 16:10:27 vhs-4 kernel: [ 0.139769] pci 0000:01:00.0: PME# supported from D0 D1 D2
Feb 28 16:10:27 vhs-4 kernel: [ 0.139820] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
Feb 28 16:10:27 vhs-4 kernel: [ 0.139828] pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139831] pci 0000:00:01.0: bridge window [mem 0xfbb00000-0xfbbfffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139890] pci 0000:00:1c.0: PCI bridge to [bus 02]
Feb 28 16:10:27 vhs-4 kernel: [ 0.139954] pci 0000:00:1c.1: PCI bridge to [bus 03]
Feb 28 16:10:27 vhs-4 kernel: [ 0.140050] pci 0000:04:00.0: [14e4:1691] type 00 class 0x020000
Feb 28 16:10:27 vhs-4 kernel: [ 0.140085] pci 0000:04:00.0: reg 0x10: [mem 0xfba00000-0xfba0ffff 64bit]
Feb 28 16:10:27 vhs-4 kernel: [ 0.140262] pci 0000:04:00.0: PME# supported from D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.147856] pci 0000:00:1c.2: PCI bridge to [bus 04]
Feb 28 16:10:27 vhs-4 kernel: [ 0.147865] pci 0000:00:1c.2: bridge window [mem 0xfba00000-0xfbafffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.147944] pci 0000:00:1c.3: PCI bridge to [bus 05]
Feb 28 16:10:27 vhs-4 kernel: [ 0.148040] pci 0000:06:00.0: [14e4:1691] type 00 class 0x020000
Feb 28 16:10:27 vhs-4 kernel: [ 0.148077] pci 0000:06:00.0: reg 0x10: [mem 0xfb900000-0xfb90ffff 64bit]
Feb 28 16:10:27 vhs-4 kernel: [ 0.148278] pci 0000:06:00.0: PME# supported from D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.155866] pci 0000:00:1c.4: PCI bridge to [bus 06]
Feb 28 16:10:27 vhs-4 kernel: [ 0.155875] pci 0000:00:1c.4: bridge window [mem 0xfb900000-0xfb9fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.155973] pci 0000:07:00.0: [1033:0194] type 00 class 0x0c0330
Feb 28 16:10:27 vhs-4 kernel: [ 0.156003] pci 0000:07:00.0: reg 0x10: [mem 0xfb800000-0xfb801fff 64bit]
Feb 28 16:10:27 vhs-4 kernel: [ 0.156150] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold
Feb 28 16:10:27 vhs-4 kernel: [ 0.163877] pci 0000:00:1c.5: PCI bridge to [bus 07]
Feb 28 16:10:27 vhs-4 kernel: [ 0.163885] pci 0000:00:1c.5: bridge window [mem 0xfb800000-0xfb8fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.164240] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Feb 28 16:10:27 vhs-4 kernel: [ 0.164283] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Feb 28 16:10:27 vhs-4 kernel: [ 0.164324] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Feb 28 16:10:27 vhs-4 kernel: [ 0.164365] ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
Feb 28 16:10:27 vhs-4 kernel: [ 0.164405] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
Feb 28 16:10:27 vhs-4 kernel: [ 0.164446] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
Feb 28 16:10:27 vhs-4 kernel: [ 0.164487] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
Feb 28 16:10:27 vhs-4 kernel: [ 0.164528] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)
Feb 28 16:10:27 vhs-4 kernel: [ 0.164577] ACPI: Enabled 3 GPEs in block 00 to 3F
Feb 28 16:10:27 vhs-4 kernel: [ 0.164666] vgaarb: setting as boot device: PCI:0000:00:02.0
Feb 28 16:10:27 vhs-4 kernel: [ 0.164668] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
Feb 28 16:10:27 vhs-4 kernel: [ 0.164670] vgaarb: loaded
Feb 28 16:10:27 vhs-4 kernel: [ 0.164671] vgaarb: bridge control possible 0000:00:02.0
Feb 28 16:10:27 vhs-4 kernel: [ 0.164891] SCSI subsystem initialized
Feb 28 16:10:27 vhs-4 kernel: [ 0.164924] libata version 3.00 loaded.
Feb 28 16:10:27 vhs-4 kernel: [ 0.164949] ACPI: bus type USB registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.164964] usbcore: registered new interface driver usbfs
Feb 28 16:10:27 vhs-4 kernel: [ 0.164974] usbcore: registered new interface driver hub
Feb 28 16:10:27 vhs-4 kernel: [ 0.164990] usbcore: registered new device driver usb
Feb 28 16:10:27 vhs-4 kernel: [ 0.165102] PCI: Using ACPI for IRQ routing
Feb 28 16:10:27 vhs-4 kernel: [ 0.171353] PCI: pci_cache_line_size set to 64 bytes
Feb 28 16:10:27 vhs-4 kernel: [ 0.171403] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.171404] e820: reserve RAM buffer [mem 0xb6d6e000-0xb7ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.171406] e820: reserve RAM buffer [mem 0xb6df7000-0xb7ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.171408] e820: reserve RAM buffer [mem 0xb7000000-0xb7ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.171409] e820: reserve RAM buffer [mem 0x440600000-0x443ffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.171513] NetLabel: Initializing
Feb 28 16:10:27 vhs-4 kernel: [ 0.171515] NetLabel: domain hash size = 128
Feb 28 16:10:27 vhs-4 kernel: [ 0.171516] NetLabel: protocols = UNLABELED CIPSOv4
Feb 28 16:10:27 vhs-4 kernel: [ 0.171528] NetLabel: unlabeled traffic allowed by default
Feb 28 16:10:27 vhs-4 kernel: [ 0.171584] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Feb 28 16:10:27 vhs-4 kernel: [ 0.171588] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Feb 28 16:10:27 vhs-4 kernel: [ 0.173629] Switched to clocksource hpet
Feb 28 16:10:27 vhs-4 kernel: [ 0.178695] pnp: PnP ACPI init
Feb 28 16:10:27 vhs-4 kernel: [ 0.178713] ACPI: bus type PNP registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.178819] system 00:00: [mem 0xfed10000-0xfed19fff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.178822] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.178823] system 00:00: [mem 0xfed90000-0xfed93fff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.178825] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.178827] system 00:00: [mem 0xfee00000-0xfee0ffff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.178830] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.178905] system 00:01: [io 0x0a30-0x0a3f] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.178908] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.178956] pnp 00:02: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179003] pnp 00:03: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179114] pnp 00:04: [dma 0 disabled]
Feb 28 16:10:27 vhs-4 kernel: [ 0.179157] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179186] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179231] system 00:06: [io 0x04d0-0x04d1] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179233] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179377] system 00:07: [io 0x0400-0x0453] could not be reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179379] system 00:07: [io 0x0458-0x047f] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179381] system 00:07: [io 0x1180-0x119f] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179383] system 00:07: [io 0x0500-0x057f] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179385] system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179387] system 00:07: [mem 0xfec00000-0xfecfffff] could not be reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179389] system 00:07: [mem 0xfed08000-0xfed08fff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179391] system 00:07: [mem 0xff000000-0xffffffff] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179393] system 00:07: Plug and Play ACPI device, IDs PNP0c01 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179443] system 00:08: [io 0x0454-0x0457] has been reserved
Feb 28 16:10:27 vhs-4 kernel: [ 0.179446] system 00:08: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Feb 28 16:10:27 vhs-4 kernel: [ 0.179602] pnp: PnP ACPI: found 9 devices
Feb 28 16:10:27 vhs-4 kernel: [ 0.179603] ACPI: bus type PNP unregistered
Feb 28 16:10:27 vhs-4 kernel: [ 0.186112] pci 0000:00:01.0: PCI bridge to [bus 01]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186116] pci 0000:00:01.0: bridge window [mem 0xfbb00000-0xfbbfffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186121] pci 0000:00:1c.0: PCI bridge to [bus 02]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186132] pci 0000:00:1c.1: PCI bridge to [bus 03]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186143] pci 0000:00:1c.2: PCI bridge to [bus 04]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186149] pci 0000:00:1c.2: bridge window [mem 0xfba00000-0xfbafffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186157] pci 0000:00:1c.3: PCI bridge to [bus 05]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186168] pci 0000:00:1c.4: PCI bridge to [bus 06]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186174] pci 0000:00:1c.4: bridge window [mem 0xfb900000-0xfb9fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186181] pci 0000:00:1c.5: PCI bridge to [bus 07]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186187] pci 0000:00:1c.5: bridge window [mem 0xfb800000-0xfb8fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186196] pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186198] pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186199] pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186201] pci_bus 0000:00: resource 7 [io 0x0d00-0xffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186202] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186204] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186206] pci_bus 0000:00: resource 10 [mem 0xbfa00000-0xffffffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186207] pci_bus 0000:01: resource 1 [mem 0xfbb00000-0xfbbfffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186209] pci_bus 0000:04: resource 1 [mem 0xfba00000-0xfbafffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186211] pci_bus 0000:06: resource 1 [mem 0xfb900000-0xfb9fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186213] pci_bus 0000:07: resource 1 [mem 0xfb800000-0xfb8fffff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.186239] NET: Registered protocol family 2
Feb 28 16:10:27 vhs-4 kernel: [ 0.186440] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.186677] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.186803] TCP: Hash tables configured (established 131072 bind 65536)
Feb 28 16:10:27 vhs-4 kernel: [ 0.186821] TCP: reno registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.186838] UDP hash table entries: 8192 (order: 6, 262144 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.186898] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.186978] NET: Registered protocol family 1
Feb 28 16:10:27 vhs-4 kernel: [ 0.186992] pci 0000:00:02.0: Video device with shadowed ROM
Feb 28 16:10:27 vhs-4 kernel: [ 0.187329] PCI: CLS 64 bytes, default 64
Feb 28 16:10:27 vhs-4 kernel: [ 0.187378] Trying to unpack rootfs image as initramfs...
Feb 28 16:10:27 vhs-4 kernel: [ 0.641878] Freeing initrd memory: 29596K (ffff88001e309000 - ffff88001fff0000)
Feb 28 16:10:27 vhs-4 kernel: [ 0.641888] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Feb 28 16:10:27 vhs-4 kernel: [ 0.641890] software IO TLB [mem 0xb2d6e000-0xb6d6e000] (64MB) mapped at [ffff8800b2d6e000-ffff8800b6d6dfff]
Feb 28 16:10:27 vhs-4 kernel: [ 0.642147] RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
Feb 28 16:10:27 vhs-4 kernel: [ 0.642217] microcode: CPU0 sig=0x206a7, pf=0x2, revision=0x25
Feb 28 16:10:27 vhs-4 kernel: [ 0.642224] microcode: CPU1 sig=0x206a7, pf=0x2, revision=0x25
Feb 28 16:10:27 vhs-4 kernel: [ 0.642232] microcode: CPU2 sig=0x206a7, pf=0x2, revision=0x25
Feb 28 16:10:27 vhs-4 kernel: [ 0.642240] microcode: CPU3 sig=0x206a7, pf=0x2, revision=0x25
Feb 28 16:10:27 vhs-4 kernel: [ 0.642289] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Feb 28 16:10:27 vhs-4 kernel: [ 0.642313] Scanning for low memory corruption every 60 seconds
Feb 28 16:10:27 vhs-4 kernel: [ 0.642588] futex hash table entries: 1024 (order: 4, 65536 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.642605] Initialise system trusted keyring
Feb 28 16:10:27 vhs-4 kernel: [ 0.642627] audit: initializing netlink subsys (disabled)
Feb 28 16:10:27 vhs-4 kernel: [ 0.642639] audit: type=2000 audit(1677597011.632:1): initialized
Feb 28 16:10:27 vhs-4 kernel: [ 0.643011] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Feb 28 16:10:27 vhs-4 kernel: [ 0.644433] zpool: loaded
Feb 28 16:10:27 vhs-4 kernel: [ 0.644436] zbud: loaded
Feb 28 16:10:27 vhs-4 kernel: [ 0.644582] VFS: Disk quotas dquot_6.5.2
Feb 28 16:10:27 vhs-4 kernel: [ 0.644616] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Feb 28 16:10:27 vhs-4 kernel: [ 0.645039] fuse init (API version 7.23)
Feb 28 16:10:27 vhs-4 kernel: [ 0.645121] msgmni has been set to 31805
Feb 28 16:10:27 vhs-4 kernel: [ 0.645172] Key type big_key registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.645536] Key type asymmetric registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.645540] Asymmetric key parser 'x509' registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.645572] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Feb 28 16:10:27 vhs-4 kernel: [ 0.645611] io scheduler noop registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.645614] io scheduler deadline registered (default)
Feb 28 16:10:27 vhs-4 kernel: [ 0.645659] io scheduler cfq registered
Feb 28 16:10:27 vhs-4 kernel: [ 0.645808] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.645921] pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.646044] pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.646161] pcieport 0000:00:1c.2: irq 43 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.646301] pcieport 0000:00:1c.3: irq 44 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.646419] pcieport 0000:00:1c.4: irq 45 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.646499] pcieport 0000:00:1c.5: irq 46 for MSI/MSI-X
Feb 28 16:10:27 vhs-4 kernel: [ 0.646581] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Feb 28 16:10:27 vhs-4 kernel: [ 0.646583] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Feb 28 16:10:27 vhs-4 kernel: [ 0.646586] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Feb 28 16:10:27 vhs-4 kernel: [ 0.646603] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Feb 28 16:10:27 vhs-4 kernel: [ 0.646607] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Feb 28 16:10:27 vhs-4 kernel: [ 0.646624] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
Feb 28 16:10:27 vhs-4 kernel: [ 0.646628] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
jm@jm-OptiPlex-9020:~$ Hors ligne