MDS 9124e - Port 'Externally Disabled'
Hi Guys
Hoping you can help with this one..
On a MDS9124e switch installed in a HP C-Class Blade Enclosure I am seeing the port status as 'Externally Disabled' The port has acquired a license OK but will not come up.
The same problem was refrenced at http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Data%20Center&topic=Storage%20Networking&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddf9f63/0#selected_message
But I cannot find any settings in the HP Onboard Admin that would enable a port on the fabric switch.
Any help would be greatly appreciated.
Thanks
Stuart
Hi Phil
The Onboad Administrator Port Mapping for the 9124e in question was showing as connected on that port which was why I thought it was strange that the port was showing as 'extDisabled' on the switch in 'show interface brief'.
The blade is at a remote side so this morning I had the HBA mez card reseated and the port has now come up on the switch, not sure if it was the reseating of the card or the insertion of the blade into the enclosure that cured it.
Thanks for your reply!!
Stuart
Similar Messages
-
I keep getting error 3004 when i try restoring and updateing my iphone 4 to iOS 7 i did everything 1. flushed dns 2. edited hosts 3. updated itunes and downloaded new one 4. switched usb ports 5. disabled antivirus 6. enabled ports 80 and 443 7. disabled firewall 8. even tryed putting mobile in DFU mode to restore it not of this worked so please help me
please replyyy i'm stuck on this like whole week
-
The Cisco MDS 9000 Port Analyzer Adapter
Hi,
At my client place, we are having an issue with BackUp via TSM and a library.
We would like to analyse the traffic that pass in the Fiber Channel of our MDS-9513.
From what we saw, Wireshark, our soft to analyse network traffic is only using NIC card to analyse.
Is the only way to analyse the FC traffic to pass via "The Cisco MDS 9000 Port Analyzer Adapter" ?
If that is the only way, is there a way tor ent this equipment for the time necesery to analyse our trace ?
Thank you in advance for you help.
Christian CarrierThe Cisco Traffic Analyzer provides real-time analysis of SPAN traffic or analysis of captured traffic through a Web browser user interface. Traffic encapsulated by one or more Port Analyzer Adapters can be analyzed concurrently with a single PC and ntop, which is public domain software enhanced by Cisco for Fibre Channel traffic analysis. This Cisco Traffic Analyzer solution enables you to quickly determine the throughput for traffic between specific Fibre Channel sources and destinations, all traffic in a particular Virtual SAN (VSAN), or all network traffic. Round trip response times, SCSI I/Os per second, SCSI read vs. write traffic throughput and frame counts, SCSI session status and management task information are provided. Additional statistics are also available on Fibre Channel frame sizes and network management protocols.
For further information click this link.
http://www.cisco.com/en/US/products/hw/ps4159/ps4358/products_data_sheet09186a0080142d34.html#wp1002317 -
My USB ports get disabled on my iMac when in sleep mode
I can't seem to figure this out. When waking from sleep mode, all my USB ports are disabled. I first noticed it when the USB speakers stopped working, but none of the ports work, to the printer, or to the scanner. The only way to reactivate the ports is to do a restart. I did a virus scan of my entire HD but it found nothing. I have not installed any new software recently so I'm stumped. I'm hoping this isn't a hardware issue.
Sometimes, a computer has a problem remapping your USB devices after sleep. Disconnect all of your USB devices: printers, mice, scanners, everything. Wait a minute. Reinsert the devices. This resets your USB map.
-
Port N disabled by hub (EMI?), re-enabling (USB transfer unstable)
Hi all,
I have experienced highly unstable data transfer to/from my USB stick and USB attached memory card reader for the last 5 days or so. Everytime I try to copy data to or from these devices the transfer ends up in hundreds of I/O Errors due to resets of the devices by the hub.
I have kernel 3.9.2-1 running
Here is the relevant part of dmesg output:
[10789.332431] sd 9:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[10789.333675] sd 9:0:0:0: [sdb] No Caching mode page present
[10789.333688] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[10789.339037] sd 9:0:0:0: [sdb] No Caching mode page present
[10789.339049] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[10789.358023] sdb: sdb1 sdb2
[10816.262052] EXT4-fs (sdb2): mounting ext3 file system using the ext4 subsystem
[10816.453752] EXT4-fs (sdb2): recovery complete
[10816.455752] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
[10910.900018] hub 5-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
[10911.005676] usb 5-1: reset high-speed USB device number 2 using ehci-pci
[10911.285822] usb 5-1: USB disconnect, device number 2
[10911.286632] sd 9:0:0:0: [sdb] Unhandled error code
[10911.286642] sd 9:0:0:0: [sdb]
[10911.286647] Result: hostbyte=0x01 driverbyte=0x00
[10911.286653] sd 9:0:0:0: [sdb] CDB:
[10911.286657] cdb[0]=0x28: 28 00 01 b0 fc d1 00 00 f0 00
[10911.286675] end_request: I/O error, dev sdb, sector 28376273
[10911.286736] sd 9:0:0:0: [sdb] Unhandled error code
[10911.286742] sd 9:0:0:0: [sdb]
[10911.286745] Result: hostbyte=0x01 driverbyte=0x00
[10911.286750] sd 9:0:0:0: [sdb] CDB:
[10911.286753] cdb[0]=0x28: 28 00 01 b0 fd c1 00 00 10 00
[10911.286768] end_request: I/O error, dev sdb, sector 28376513
[10911.291788] Aborting journal on device sdb2-8.
[10911.291821] JBD2: Error -5 detected when updating journal superblock for sdb2-8.
[10911.293613] journal commit I/O error
[10911.341264] journal commit I/O error
[10911.341277] journal commit I/O error
[10911.341279] journal commit I/O error
[10911.341280] journal commit I/O error
[10911.341282] journal commit I/O error
[10911.341290] journal commit I/O error
[10911.341292] journal commit I/O error
[10911.341293] journal commit I/O error
[10911.341297] journal commit I/O error
[10911.341298] journal commit I/O error
[10911.341307] journal commit I/O error
[10911.341308] journal commit I/O error
[10911.341314] journal commit I/O error
[10911.341340] journal commit I/O error
[10911.341345] journal commit I/O error
[10911.341347] journal commit I/O error
[10911.341348] journal commit I/O error
[10911.341349] journal commit I/O error
[10911.342604] journal commit I/O error
[10911.342606] journal commit I/O error
[10911.342608] journal commit I/O error
[10911.342614] journal commit I/O error
[10911.342615] journal commit I/O error
[10911.342622] journal commit I/O error
[10911.342623] journal commit I/O error
[10911.342625] journal commit I/O error
[10911.342626] journal commit I/O error
[10911.342636] journal commit I/O error
[10911.342637] journal commit I/O error
[10911.342654] journal commit I/O error
[10911.342658] journal commit I/O error
[10911.342677] journal commit I/O error
[10911.342894] journal commit I/O error
[10911.342958] journal commit I/O error
[10911.343023] journal commit I/O error
[10911.343024] journal commit I/O error
[10911.343026] journal commit I/O error
[10911.343027] journal commit I/O error
[10911.343028] journal commit I/O error
[10911.343030] journal commit I/O error
[10911.343031] journal commit I/O error
[10911.343033] journal commit I/O error
[10911.343035] journal commit I/O error
[10911.343036] journal commit I/O error
[10911.343038] journal commit I/O error
[10911.343039] journal commit I/O error
[10911.343041] journal commit I/O error
[10911.343042] journal commit I/O error
[10911.343044] journal commit I/O error
[10911.343048] journal commit I/O error
[10911.343049] journal commit I/O error
[10911.343051] journal commit I/O error
[10911.343052] journal commit I/O error
[10911.343174] journal commit I/O error
[10911.343175] journal commit I/O error
[10911.343176] journal commit I/O error
[10911.343178] journal commit I/O error
[10911.343179] journal commit I/O error
[10911.343180] journal commit I/O error
[10911.343186] journal commit I/O error
[10911.343187] journal commit I/O error
[10911.343189] journal commit I/O error
[10911.343191] journal commit I/O error
[10911.343193] journal commit I/O error
[10911.343195] journal commit I/O error
[10911.343196] journal commit I/O error
[10911.343197] journal commit I/O error
[10911.343199] journal commit I/O error
[10911.343200] journal commit I/O error
[10911.343202] journal commit I/O error
[10911.343204] journal commit I/O error
[10911.343206] journal commit I/O error
[10911.343208] journal commit I/O error
[10911.343209] journal commit I/O error
[10911.343211] journal commit I/O error
[10911.343216] journal commit I/O error
[10911.343218] journal commit I/O error
[10911.343220] journal commit I/O error
[10911.343221] journal commit I/O error
[10911.343223] journal commit I/O error
[10911.343224] journal commit I/O error
[10911.343226] journal commit I/O error
[10911.343227] journal commit I/O error
[10911.343229] journal commit I/O error
[10911.343231] journal commit I/O error
[10911.343232] journal commit I/O error
[10911.343234] journal commit I/O error
[10911.343236] journal commit I/O error
[10911.343238] journal commit I/O error
[10911.343240] journal commit I/O error
[10911.343242] journal commit I/O error
[10911.343243] journal commit I/O error
[10911.343245] journal commit I/O error
[10911.343246] journal commit I/O error
[10911.343249] journal commit I/O error
[10911.343250] journal commit I/O error
[10911.343252] journal commit I/O error
[10911.343254] journal commit I/O error
[10911.343256] journal commit I/O error
[10911.343258] journal commit I/O error
[10911.343260] journal commit I/O error
[10911.343262] journal commit I/O error
[10911.343264] journal commit I/O error
[10911.343265] journal commit I/O error
[10911.343267] journal commit I/O error
[10911.343268] journal commit I/O error
[10911.343270] journal commit I/O error
[10911.343272] journal commit I/O error
[10911.343274] journal commit I/O error
[10911.343276] journal commit I/O error
[10911.343277] journal commit I/O error
[10911.343279] journal commit I/O error
[10911.343281] journal commit I/O error
[10911.343283] journal commit I/O error
[10911.343285] journal commit I/O error
[10911.343287] journal commit I/O error
[10911.343288] journal commit I/O error
[10911.343289] journal commit I/O error
[10911.343292] journal commit I/O error
[10911.343294] journal commit I/O error
[10911.343296] journal commit I/O error
[10911.343297] journal commit I/O error
[10911.343299] journal commit I/O error
[10911.343301] journal commit I/O error
[10911.343303] journal commit I/O error
[10911.343304] journal commit I/O error
[10911.343305] journal commit I/O error
[10911.343308] journal commit I/O error
[10911.343309] journal commit I/O error
[10911.343311] journal commit I/O error
[10911.343312] journal commit I/O error
[10911.343315] journal commit I/O error
[10911.343317] journal commit I/O error
[10911.343319] journal commit I/O error
[10911.343320] journal commit I/O error
[10911.343322] journal commit I/O error
[10911.343323] journal commit I/O error
[10911.343324] journal commit I/O error
[10911.343326] journal commit I/O error
[10911.343327] journal commit I/O error
[10911.343329] journal commit I/O error
[10911.343331] journal commit I/O error
[10911.343333] journal commit I/O error
[10911.343335] journal commit I/O error
[10911.343337] journal commit I/O error
[10911.343341] journal commit I/O error
[10911.343343] journal commit I/O error
[10911.343345] journal commit I/O error
[10911.343347] journal commit I/O error
[10911.343349] journal commit I/O error
[10911.343350] journal commit I/O error
[10911.343351] journal commit I/O error
[10911.343353] journal commit I/O error
[10911.343354] journal commit I/O error
[10911.343357] journal commit I/O error
[10911.343358] journal commit I/O error
[10911.343360] journal commit I/O error
[10911.343362] journal commit I/O error
[10911.343364] journal commit I/O error
[10911.343366] journal commit I/O error
[10911.343367] journal commit I/O error
[10911.343369] journal commit I/O error
[10911.343371] journal commit I/O error
[10911.343372] journal commit I/O error
[10911.343373] journal commit I/O error
[10911.343375] journal commit I/O error
[10911.343377] journal commit I/O error
[10911.343379] journal commit I/O error
[10911.343380] journal commit I/O error
[10911.343382] journal commit I/O error
[10911.343383] journal commit I/O error
[10911.343384] journal commit I/O error
[10911.343386] journal commit I/O error
[10911.343387] journal commit I/O error
[10911.343390] journal commit I/O error
[10911.343391] journal commit I/O error
[10911.343392] journal commit I/O error
[10911.343394] journal commit I/O error
[10911.343395] journal commit I/O error
[10911.343397] journal commit I/O error
[10911.343398] journal commit I/O error
[10911.343400] journal commit I/O error
[10911.343401] journal commit I/O error
[10911.343403] journal commit I/O error
[10911.343404] journal commit I/O error
[10911.343405] journal commit I/O error
[10911.343407] journal commit I/O error
[10911.343408] journal commit I/O error
[10911.343410] journal commit I/O error
[10911.343412] journal commit I/O error
[10911.343414] journal commit I/O error
[10911.343416] journal commit I/O error
[10911.343419] journal commit I/O error
[10911.343420] journal commit I/O error
[10911.343422] journal commit I/O error
[10911.343423] journal commit I/O error
[10911.343425] journal commit I/O error
[10911.343426] journal commit I/O error
[10911.343429] journal commit I/O error
[10911.343431] journal commit I/O error
[10911.343432] journal commit I/O error
[10911.343434] journal commit I/O error
[10911.343435] journal commit I/O error
[10911.343437] journal commit I/O error
[10911.343439] journal commit I/O error
[10911.343441] journal commit I/O error
[10911.343443] journal commit I/O error
[10911.343445] journal commit I/O error
[10911.343446] journal commit I/O error
[10911.343448] journal commit I/O error
[10911.343449] journal commit I/O error
[10911.343451] journal commit I/O error
[10911.343453] journal commit I/O error
[10911.343455] journal commit I/O error
[10911.343457] journal commit I/O error
[10911.343459] journal commit I/O error
[10911.343461] journal commit I/O error
[10911.343463] journal commit I/O error
[10911.343465] journal commit I/O error
[10911.343466] journal commit I/O error
[10911.343468] journal commit I/O error
[10911.343470] journal commit I/O error
[10911.343471] journal commit I/O error
[10911.343473] journal commit I/O error
[10911.343474] journal commit I/O error
[10911.343476] journal commit I/O error
[10911.343478] journal commit I/O error
[10911.343479] journal commit I/O error
[10911.343481] journal commit I/O error
[10911.343483] journal commit I/O error
[10911.343487] journal commit I/O error
[10911.343489] journal commit I/O error
[10911.343490] journal commit I/O error
[10911.343491] journal commit I/O error
[10911.343494] journal commit I/O error
[10911.343495] journal commit I/O error
[10911.343497] journal commit I/O error
[10911.343498] journal commit I/O error
[10911.343500] journal commit I/O error
[10911.343502] journal commit I/O error
[10911.343503] journal commit I/O error
[10911.343505] journal commit I/O error
[10911.343507] journal commit I/O error
[10911.343508] journal commit I/O error
[10911.343510] journal commit I/O error
[10911.343512] journal commit I/O error
[10911.343514] journal commit I/O error
[10911.343515] journal commit I/O error
[10911.343517] journal commit I/O error
[10911.343519] journal commit I/O error
[10911.343521] journal commit I/O error
[10911.343522] journal commit I/O error
[10911.343524] journal commit I/O error
[10911.343526] journal commit I/O error
[10911.343527] journal commit I/O error
[10911.343529] journal commit I/O error
[10911.343531] journal commit I/O error
[10911.343533] journal commit I/O error
[10911.343534] journal commit I/O error
[10911.343536] journal commit I/O error
[10911.343538] journal commit I/O error
[10911.343539] journal commit I/O error
[10911.343541] journal commit I/O error
[10911.343543] journal commit I/O error
[10911.343545] journal commit I/O error
[10911.343546] journal commit I/O error
[10911.343548] journal commit I/O error
[10911.343551] journal commit I/O error
[10911.343552] journal commit I/O error
[10911.343553] journal commit I/O error
[10911.343555] journal commit I/O error
[10911.343557] journal commit I/O error
[10911.343558] journal commit I/O error
[10911.343560] journal commit I/O error
[10911.343562] journal commit I/O error
[10911.343565] journal commit I/O error
[10911.343566] journal commit I/O error
[10911.343568] journal commit I/O error
[10911.343569] journal commit I/O error
[10911.343571] journal commit I/O error
[10911.343573] journal commit I/O error
[10911.343575] journal commit I/O error
[10911.343576] journal commit I/O error
[10911.343578] journal commit I/O error
[10911.343580] journal commit I/O error
[10911.343581] journal commit I/O error
[10911.343583] journal commit I/O error
[10911.343584] journal commit I/O error
[10911.343586] journal commit I/O error
[10911.343588] journal commit I/O error
[10911.343590] journal commit I/O error
[10911.343591] journal commit I/O error
[10911.343593] journal commit I/O error
[10911.343594] journal commit I/O error
[10911.343596] journal commit I/O error
[10911.343598] journal commit I/O error
[10911.343599] journal commit I/O error
[10911.343600] journal commit I/O error
[10911.343603] journal commit I/O error
[10911.343604] journal commit I/O error
[10911.343606] journal commit I/O error
[10911.343608] journal commit I/O error
[10911.343609] journal commit I/O error
[10911.343611] journal commit I/O error
[10911.343613] journal commit I/O error
[10911.343615] journal commit I/O error
[10911.343617] journal commit I/O error
[10911.343618] journal commit I/O error
[10911.343620] journal commit I/O error
[10911.343624] journal commit I/O error
[10911.343626] journal commit I/O error
[10911.343628] journal commit I/O error
[10911.343629] journal commit I/O error
[10911.343631] journal commit I/O error
[10911.343632] journal commit I/O error
[10911.343634] journal commit I/O error
[10911.343636] journal commit I/O error
[10911.343637] journal commit I/O error
[10911.343638] journal commit I/O error
[10911.343640] journal commit I/O error
[10911.343641] journal commit I/O error
[10911.343643] journal commit I/O error
[10911.343645] journal commit I/O error
[10911.343646] journal commit I/O error
[10911.343648] journal commit I/O error
[10911.343650] journal commit I/O error
[10911.343652] journal commit I/O error
[10911.343654] journal commit I/O error
[10911.343655] journal commit I/O error
[10911.343657] journal commit I/O error
[10911.343658] journal commit I/O error
[10911.343660] journal commit I/O error
[10911.343661] journal commit I/O error
[10911.343663] journal commit I/O error
[10911.343664] journal commit I/O error
[10911.343666] journal commit I/O error
[10911.343668] journal commit I/O error
[10911.343669] journal commit I/O error
[10911.343671] journal commit I/O error
[10911.343674] journal commit I/O error
[10911.343675] journal commit I/O error
[10911.343677] journal commit I/O error
[10911.343679] journal commit I/O error
[10911.343680] journal commit I/O error
[10911.343682] journal commit I/O error
[10911.343684] journal commit I/O error
[10911.343686] journal commit I/O error
[10911.343688] journal commit I/O error
[10911.343690] journal commit I/O error
[10911.343691] journal commit I/O error
[10911.343693] journal commit I/O error
[10911.343694] journal commit I/O error
[10911.343697] journal commit I/O error
[10911.343699] journal commit I/O error
[10911.343700] journal commit I/O error
[10911.343703] journal commit I/O error
[10911.343705] journal commit I/O error
[10911.343706] journal commit I/O error
[10911.343707] journal commit I/O error
[10911.343710] journal commit I/O error
[10911.343711] journal commit I/O error
[10911.343713] journal commit I/O error
[10911.343715] journal commit I/O error
[10911.343716] journal commit I/O error
[10911.343718] journal commit I/O error
[10911.343720] journal commit I/O error
[10911.343721] journal commit I/O error
[10911.343724] journal commit I/O error
[10911.343726] journal commit I/O error
[10911.343739] journal commit I/O error
[10911.343743] journal commit I/O error
[10911.343744] journal commit I/O error
[10911.343745] journal commit I/O error
[10911.343747] journal commit I/O error
[10911.343748] journal commit I/O error
[10911.343750] journal commit I/O error
[10911.343751] journal commit I/O error
[10911.343752] journal commit I/O error
[10911.343754] journal commit I/O error
[10911.343755] journal commit I/O error
[10911.343757] journal commit I/O error
[10911.343758] journal commit I/O error
[10911.343759] journal commit I/O error
[10911.343760] journal commit I/O error
[10911.343770] journal commit I/O error
[10911.343842] journal commit I/O error
[10911.343982] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.343996] EXT4-fs error (device sdb2): ext4_journal_start_sb:349: Detected aborted journal
[10911.343998] EXT4-fs (sdb2): Remounting filesystem read-only
[10911.344000] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.344662] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.344674] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #11: block 948: comm rsync: unable to read itable block
[10911.351446] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.351457] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #342049: block 1376258: comm rsync: unable to read itable block
[10911.351676] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.351684] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #211745: block 851970: comm rsync: unable to read itable block
[10911.351894] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.351901] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #276897: block 1114114: comm rsync: unable to read itable block
[10911.351903] journal commit I/O error
[10911.352117] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.352124] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #309473: block 1245186: comm rsync: unable to read itable block
[10911.352337] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.352344] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #65153: block 262146: comm rsync: unable to read itable block
[10911.352346] journal commit I/O error
[10911.352882] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.352889] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #97729: block 393218: comm rsync: unable to read itable block
[10911.353108] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.353115] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #439777: block 1769474: comm rsync: unable to read itable block
[10911.353117] journal commit I/O error
[10911.353427] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.353435] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #529361: block 2129922: comm rsync: unable to read itable block
[10911.353436] journal commit I/O error
[10911.353702] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.353709] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #545649: block 2195458: comm rsync: unable to read itable block
[10911.354550] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.354561] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #667809: block 2686978: comm rsync: unable to read itable block
[10911.354892] EXT4-fs (sdb2): previous I/O error to superblock detected
[10911.354899] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #415345: block 1671170: comm rsync: unable to read itable block
[10911.355183] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #513073: block 2064386: comm rsync: unable to read itable block
[10911.356842] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.356950] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357046] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357142] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357236] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357331] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357425] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357518] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357611] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357705] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357798] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.357892] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358005] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358101] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358197] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358290] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358385] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358478] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358572] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358666] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358759] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358852] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.358945] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359040] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359134] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359228] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359321] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359415] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359509] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359603] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359697] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359791] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.359964] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360060] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360155] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360248] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360342] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360435] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360527] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360620] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360712] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360805] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360873] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360907] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360949] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.360983] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361016] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361050] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361082] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361338] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361371] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361404] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361437] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361477] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361512] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.361545] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366222] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366336] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366431] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366524] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366617] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366711] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366803] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366896] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.366989] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.367081] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.367084] journal commit I/O error
[10911.375505] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.375507] journal commit I/O error
[10911.375922] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376025] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376125] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376233] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376340] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376341] journal commit I/O error
[10911.376448] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376554] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376661] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376767] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376874] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.376980] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377087] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377194] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377301] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377408] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377515] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377621] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377728] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377835] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.377950] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378059] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378167] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378274] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378382] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378491] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378600] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378709] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.378818] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379006] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379134] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379244] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379353] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379461] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379569] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379677] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379785] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.379893] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380002] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380113] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380163] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380213] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380364] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380580] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380643] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380691] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380739] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380803] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380862] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.380974] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381032] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381091] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381147] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381206] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381256] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381305] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381352] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381399] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381446] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381492] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381538] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381584] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381630] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381676] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381722] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381768] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381814] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381883] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381939] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.381997] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382066] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382068] journal commit I/O error
[10911.382169] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382227] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382229] journal commit I/O error
[10911.382285] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382343] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382390] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382437] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382495] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382554] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382634] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382689] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382737] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382785] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382832] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382880] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382927] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.382984] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383042] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383088] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383192] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383241] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383293] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383347] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383389] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383436] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383482] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383530] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383576] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383618] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383664] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383710] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383751] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383793] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383835] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383883] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383925] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.383972] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384018] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384060] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384106] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384152] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384199] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384245] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384292] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384338] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384384] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384431] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384478] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384524] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384570] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384752] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384809] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384861] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384908] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.384972] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.385086] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.385134] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.385175] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.385221] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.385276] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.404796] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.404890] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.404949] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405006] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405062] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405119] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405176] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405231] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405287] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405345] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405401] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405458] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405514] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405570] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405626] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405682] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405762] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405822] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405877] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405933] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.405989] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406044] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406100] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406167] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406226] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406298] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406367] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406425] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406492] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406551] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406606] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406661] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406717] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406787] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406882] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.406978] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407047] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407115] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407181] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407238] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407292] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407346] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407400] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407455] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407521] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407578] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407633] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407710] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407767] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.407823] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411249] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411340] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411445] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411535] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411622] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411709] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411794] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411878] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.411961] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412043] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412126] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412208] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412314] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412406] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412497] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412585] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412673] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412761] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412850] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.412939] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413028] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413118] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413206] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413294] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413382] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413518] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413637] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413705] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413798] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.413888] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414053] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414210] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414332] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414403] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414552] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414623] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414710] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414800] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414890] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.414980] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415090] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415183] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415272] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415361] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415450] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415538] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415627] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415719] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415823] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.415925] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416015] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416104] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416192] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416281] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416370] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416472] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416587] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416711] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416836] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.416937] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417027] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417116] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417206] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417295] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417384] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417473] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417576] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417678] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417770] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417883] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itable block
[10911.417933] EXT4-fs error (device sdb2): __ext4_get_inode_loc:3761: inode #293185: block 1179650: comm rsync: unable to read itablePerhaps a bad cable...or if using hub...a reset occured....overload of the 5v current limit
-
MDS FC Port mode for UCS connectivity
Hi,
A little question on admin mode of the MDS switch port which is connected to a UCS Fabric Interconnect.
The switch is a MDS 9509 running SAN OS v3.3, we have enabled NPIV on the MDS switch. Currently the port's admin mode is 'auto' and its operational mode is 'F'.
Therefore is it safe to change the admin mode to 'F' or is it better to keep 'auto' as it is.
Cheers,
KisankaThanks Jeramy. Since the final operational mode is F, is it safe to administratively set the mode to 'F'
-
Netflix: HTTP port is disabled / blocked by firewall - how to fix?
Hi there. I've been using Netflix for over a year with no issues. I don't have Internet T, but the service is available via my Samsung Blueray. My Blueray is linked into my Time capsule. I'm now trying to set up Netflix US via a DNS. I set up the DNS instructions on my MAC, and they work great (I had Netflix on my computer before - this is an enhanced service).
To see Netflix US on the big screen, I had to make some changes to the Network settings on the BR player, which involved manually setting the IP, Subnet mask , Gateway and DNS server. And now Netflix does not work. My Blureray is communicating with my Mac / Time Capsule but NOT the Internet. When I do a Network test, the Mac address, the IP, Subnet, and Gateway ping all check, but the Internet Service Test fails with the following message:
"The HTTP port is disabled. Please check if the HTTP pot is blocked by something like the internet firewall program".
Ploblem is, I don't know how to do that (I am not exactly Mac savvy - still working on that). How do I check this internet firewall program, and how do I enable it? I am sure it is something simple, but I do not know what it is.
I did see other similar issues with Netflix, but not like this one. If I go back to the automatic settings on the BR (I have to enter my password for the Time Capsule), I get Netflix again.
Thank you! Hope someone can assist. I'd love to be able to get Netflix US working on my BR / TV big screen, not just on my Mac.redhead2 wrote:
Ploblem is, I don't know how to do that (I am not exactly Mac savvy - still working on that). How do I check this internet firewall program, and how do I enable it? I am sure it is something simple, but I do not know what it is.
System Preferences/Security/Firewall - should be on.
Not sure if this article will help - Mac OS X v10.5, 10.6: About the Application Firewall
Not even sure if any solution will work as Macs are not compatible with Blue Ray. -
Hello all,
I got a new c7000 with some MDS swithes. I'm trying to get to the latest software. I started at 4.1.x and can only get to 4.2.9. I'm then trying to upgrade to 5.0.4d it fails. In Fabric Manager it fails during copying and when i try to install via CLI i get the following:
-- FAIL. Return code 0x 0 (success).
Install has failed. Return code 0x40930068 (Runtime check failed).
Please identify the cause of the failure, and try 'install all' again.
Currently i have 5.0.7 FM installed. So question is can i get to 5.0?
Another question is can i get to 5.2.2 with using FM 5.0.7? Or do i have to install DCNM?
Thanks for your time and support,
NickYou can map internal to external using VSANs...Put the blade in slot x in vsan xxx and the external internal interface also into vsan xxx.
The real question is why you need to do this? The external ports are usually used for ISLs to a core swtich, and they can be TE ports which carry multiple VSANs.
If you install a storage unit into one of the external ports, you can limit access by zoning. The blade port and the external port would need to be in the same VSAN, and then on that VSAN you can create a zone/zoneset to permit the blade to access the storage port.
There really is no need to map traffic between the internal and external ports per se.
If you can provide more details as to what you need to accomplish, we can provide a more accurate reply.
Unless you are well versed in FSPF and fiber channel routing, I would steer clear of the fcroute commands or you could end up with asymetric traffic flows.
HTH,
Mike -
Upgrade MDS 9124E Fabric Switch hor HP c-Class
Hi
all SAN switches MDS95XX and MDS9124e24 port must be upgraded from NX-OS 4.1.3a to NX-OS 5.2.2d
I have no details on the process for switch HP 9124 e.
Is it disruptif . How many steps from 4.1.3a to 5.2.2d .
Generally is the process the same with HP 9124e than MDS9124
Best regardsHi Giles,
Here is more info on upgrading.
NX-OS upgrade Best Practices for MDS switches
https://supportforums.cisco.com/docs/DOC-26029
Near the bottom is a link to the Release Notes.
Table 11 in the Release Notes has the upgrade path.
Please refer to the bottom of the 9124e data sheet
http://www.cisco.com/en/US/partner/prod/collateral/ps4159/ps6409/ps5987/product_data_sheet0900aecd805f187a.html
Service and Support
Level 1 and 2 support is provided by IBM and HP for their respective blade switches.
HP Support for the 9124e
http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=us&prodTypeId=3709945&prodSeriesId=3355738&lang=en&cc=us
Regards,
David -
Nexus 5500 - Fabricpath Core Port - Error disabled. Reason:DCX-No ACK in 100 PDUs
Has anyone seen Fabricpath Core Interfaces between two Nexus 5596UP switches error-disabled because of missing DCBX Acks after 50mins?
I do not see interface errors and the peer is another 5500.
Both switches are running 5.1(3)N2(1) with this port config:
int e1/3
switchport mode fabricpath
! Cisco 5m Twinax cables
Log messages
2012 May 25 17:40:59 nexus1 %L3VM-5-FP_TPG_INTF_DOWN: Interface Ethernet1/3 down in fabricpath topology 0 - Interface down
2012 May 25 17:40:59 nexus1 %ETHPORT-5-IF_DOWN_NONE: Interface Ethernet1/3 is down (None)
2012 May 25 17:40:59 nexus1 %ISIS_FABRICPATH-5-ADJCHANGE: isis_fabricpath-default [3365] P2P adj L1 nexus5 over Ethernet1/3 - DOWN (Delete All) on MT-0
2012 May 25 17:40:59 nexus1 %CDP-5-NEIGHBOR_REMOVED: CDP Neighbor nexus5(FOX1550GDH1) on port Ethernet1/3 has been removed
2012 May 25 17:40:59 nexus1 %LLDP-5-SERVER_REMOVED: Server with Chassis ID 547f.ee63.fa88 Port ID Eth1/1 on local port Eth1/3 has been removed
2012 May 25 17:40:59 nexus1 %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet1/3 is down (Error disabled. Reason:DCX-No ACK in 100 PDUs)
RobertCan you send the output of
show lldp interface ethernet 1/3
show lldp dcbx interface ethernet 1/3
a workaround may be to disable lldp on both sides on these physical interfaces -
Get rid of mds virus, not just disabling
I contracted the dreaded mds virus. There is also something called md worker--two files, in fact.
There are quite a few posts on here on how to disable it but how do it get rid of it completely? Also will disabling or getting rid of it mean the files it infected have to be replaced? I guess it must also be on my backup drive.
Thank you to any and everyone who replies.Well, I did the first part up to the point of highlighting the drive I'd dragged into the Privacy window. I hightlighted the drive and tried to drag it back onto the desktop. When that didn't work, I hit the minus sign and was able to drag it out. Was that correct? It's not like anything seemed to be going on while it was the in Privacy window.
Perhaps you can let me know the best way I can tell if the problem has been remedied.
Thank you, Kurt. -
ISE posture requirement to check if endpoint's USP port is disabled
Hi,
I wonder if it is possible to set the disabled USP Port in the endpoints as a requirement in ISE Posture ?
Appreciate your input.
MikeIf your question pertains to the capability of the ISE disabling the USB port on a PC, then the answer is no.
Using the NAC agent, however, you can check various programs and may be able to check the condition of USB.
You would have to create a New Posture Condition and Remediations.
The condition that I will use in this example is a Registry Key.
If the key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor\Start" has a value of 3, the USB is enabled. A value of 4 is disabled.
So set a Posture Condition:
Click Policy > Policy Elements > Conditions
Choose Posture from the left menu:
Then choose Registry Condition from the left menu.
Click +Add to add a new Posture Condition:
Then you have to create Remediation Actions. Click the Results button at the top of the left Menu:
Choose Remediation Actions and choose the Remediation you want to use. I chose Link Remediation.
+Add to add a new Link Remediation:
Then choose Requirements from the left menu and create a new Remediation Result:
Of course, you can choose different remediations as necessary for your environment.
Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question. Otherwise, feel free to post follow-up questions.
Charles Moreton -
EEM on port error-disable due to UDLD
I would like to ask from the EEM community for some assistance in regards to crafting an EEM script for an ME-3800X. We have one or two appliances whereby the only uplink (TenGigabitEthernet0/1 and/or TenGigabitEthernet0/2) goes into error-disable and caused by UDLD. What I am looking for is a script to do the following:
1. If the ports TenGigabitEthernet0/1 and/or TenGigabitEthernet0/2 goes into error-disable caused by UDLD or link-flap then disable the port, wait for 5 seconds, enable the port;
2. Wait for 15 seconds and send an email.
I only want this EEM to work on the TenGigabitEthernet interfaces and I do not want the EEM script to do this on the access ports.
Error-disable recovery is a global option and there's no option to limit on a per-interface level.
Thank you in advance.Thanks for responding, Joe.
We were not able to take down the error messages but I believe they error messages could be:
%UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Te0/2, unidirectional link detected
%PM-4-ERR_DISABLE: udld error detected on Te0/2, putting Te0/2 in err-disable state
Could an EEM script be created when an error message or an event of "unidirectional link detected" occurs, do the following:
1. In privilege mode, issue the command "udld reset".
2. Wait for 30 seconds and then send an email.
Thanks for your assistance and support, Joe. -
JBD2: Error -5 in USB 3 port external HDD when copying
Hello,
I'm getting very weird error, why I connect my external harddrive to my laptop through USB3 port and try to copy some bigger amount of data. Other USB2 ports works well.
After few minutes of copying (about 2-4 minutes) disc is disconnect leaving this in dmesg:
JBD2: I/O error detected when updating journal superblock for sdc1-8
fdisk -l
Disk /dev/sdb: 465.7 GiB, 500074283008 bytes, 976707584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00076d3f
Device Boot Start End Blocks Id System
/dev/sdb1 2048 976705535 488351744 83 Linux
parted print
Model: WD My Passport 0730 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 500GB 500GB primary ext4
I also runned fsck, but that didn't find anything.
Thank you
EDIT: I also noticed that it corrupted some of the files (my gf was browsing through photo during transfer and about 5% of them are corrupted - zero size).
Last edited by Kotrfa (2014-01-21 10:13:42)Today it occured again when I was doing backups. Here is shortened output from dmesg:
[ 283.345373] usb 3-1: USB disconnect, device number 2
[ 283.365286] Aborting journal on device sdb1-8.
[ 283.365317] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 313.111295] sd 7:0:0:0: Device offlined - not ready after error recovery
[ 313.114331] sd 7:0:0:0: [sdb] Unhandled error code
[ 313.114336] sd 7:0:0:0: [sdb]
[ 313.114338] Result: hostbyte=0x01 driverbyte=0x00
[ 313.114340] sd 7:0:0:0: [sdb] CDB:
[ 313.114342] cdb[0]=0x28: 28 00 15 01 0a 30 00 00 08 00
[ 313.114350] end_request: I/O error, dev sdb, sector 352389680
[ 313.114375] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911540)
[ 313.114379] Buffer I/O error on device sdb1, logical block 100911254
[ 313.114409] Buffer I/O error on device sdb1, logical block 100911263
[ 313.114441] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911570)
[ 313.119921] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 8923456 (offset 0 size 8192 starting block 54264064)
[ 313.123852] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #11010087: comm rsync: reading directory lblock 0
[ 313.123906] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 313.123965] EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
[ 313.123970] EXT4-fs (sdb1): Remounting filesystem read-only
[ 313.123974] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 313.124130] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 313.124144] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #12981260: comm rsync: reading directory lblock 0
[ 313.124263] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 313.925753] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #11010325: block 44040241: comm rsync: unable to read itable block
[ 313.926099] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 313.926114] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #11010325: block 44040241: comm rsync: unable to read itable block
[ 313.930455] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #11010338: block 44040242: comm rsync: unable to read itable block
[ 313.930761] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #8919957: comm rsync: reading directory lblock 0
[ 314.098610] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #8919957: comm rsync: reading directory lblock 0
[ 314.098744] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #8919958: block 35652057: comm rsync: unable to read itable block
[ 314.111398] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #8919962: block 35652057: comm rsync: unable to read itable block
[ 314.170384] usb 3-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 314.185517] usb-storage 3-1:1.0: USB Mass Storage device detected
[ 314.185579] scsi8 : usb-storage 3-1:1.0
[ 314.399446] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #8919964: block 35652057: comm rsync: unable to read itable block
[ 314.664467] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #9964696: block 39846121: comm rsync: unable to read itable block
[ 315.186534] scsi 8:0:0:0: Direct-Access WD My Passport 0730 1016 PQ: 0 ANSI: 6
[ 315.186851] scsi 8:0:0:1: Enclosure WD SES Device 1016 PQ: 0 ANSI: 6
[ 315.187176] ses 8:0:0:1: Attached Enclosure device
[ 315.187720] sd 8:0:0:0: [sdc] 976707584 512-byte logical blocks: (500 GB/465 GiB)
[ 315.187964] sd 8:0:0:0: [sdc] Write Protect is off
[ 315.187967] sd 8:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 315.188233] sd 8:0:0:0: [sdc] No Caching mode page found
[ 315.188236] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 315.191689] sd 8:0:0:0: [sdc] No Caching mode page found
[ 315.191695] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 315.486923] sdc: sdc1
[ 315.487811] sd 8:0:0:0: [sdc] No Caching mode page found
[ 315.487817] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 315.487821] sd 8:0:0:0: [sdc] Attached SCSI disk
[ 316.226527] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #9964697: block 39846121: comm rsync: unable to read itable block
[ 316.344314] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3905: inode #10492043: block 41943464: comm rsync: unable to read itable block
[ 316.382787] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #17301520: comm rsync: reading directory lblock 0
[ 316.382900] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #17301506: comm rsync: reading directory lblock 0
[ 317.462488] EXT4-fs error (device sdb1): ext4_find_entry:1309: inode #17301506: comm luckybackup: reading directory lblock 0
[ 333.476676] usb 3-1: USB disconnect, device number 3
and here is full:
[ 283.345373] usb 3-1: USB disconnect, device number 2
[ 283.365286] Aborting journal on device sdb1-8.
[ 283.365317] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 313.111295] sd 7:0:0:0: Device offlined - not ready after error recovery
[ 313.114331] sd 7:0:0:0: [sdb] Unhandled error code
[ 313.114336] sd 7:0:0:0: [sdb]
[ 313.114338] Result: hostbyte=0x01 driverbyte=0x00
[ 313.114340] sd 7:0:0:0: [sdb] CDB:
[ 313.114342] cdb[0]=0x28: 28 00 15 01 0a 30 00 00 08 00
[ 313.114350] end_request: I/O error, dev sdb, sector 352389680
[ 313.114375] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911540)
[ 313.114379] Buffer I/O error on device sdb1, logical block 100911254
[ 313.114385] Buffer I/O error on device sdb1, logical block 100911255
[ 313.114388] Buffer I/O error on device sdb1, logical block 100911256
[ 313.114391] Buffer I/O error on device sdb1, logical block 100911257
[ 313.114394] Buffer I/O error on device sdb1, logical block 100911258
[ 313.114397] Buffer I/O error on device sdb1, logical block 100911259
[ 313.114400] Buffer I/O error on device sdb1, logical block 100911260
[ 313.114403] Buffer I/O error on device sdb1, logical block 100911261
[ 313.114406] Buffer I/O error on device sdb1, logical block 100911262
[ 313.114409] Buffer I/O error on device sdb1, logical block 100911263
[ 313.114441] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911570)
[ 313.114465] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911600)
[ 313.114486] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911630)
[ 313.114507] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911660)
[ 313.114530] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 10915378 (offset 0 size 1277952 starting block 100911672)
[ 313.114559] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872572 (offset 0 size 36864 starting block 32475401)
[ 313.114571] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872575 (offset 0 size 4096 starting block 32475402)
[ 313.114577] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872573 (offset 0 size 8192 starting block 32475404)
[ 313.114583] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872574 (offset 0 size 16384 starting block 32475408)
[ 313.114591] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872584 (offset 0 size 4096 starting block 32475409)
[ 313.114596] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872585 (offset 0 size 4096 starting block 32475410)
[ 313.114601] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872586 (offset 0 size 4096 starting block 32475411)
[ 313.114609] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872590 (offset 0 size 4096 starting block 32475412)
[ 313.114615] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872587 (offset 0 size 8192 starting block 32475414)
[ 313.114621] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872588 (offset 0 size 20480 starting block 32475419)
[ 313.114629] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872589 (offset 0 size 20480 starting block 32475424)
[ 313.114649] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872591 (offset 0 size 4096 starting block 32475425)
[ 313.114654] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872592 (offset 0 size 20480 starting block 32475430)
[ 313.114662] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872593 (offset 0 size 4096 starting block 32475431)
[ 313.114667] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872594 (offset 0 size 4096 starting block 32475432)
[ 313.114671] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872595 (offset 0 size 4096 starting block 32475433)
[ 313.114678] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872596 (offset 0 size 40960 starting block 32475443)
[ 313.114688] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872597 (offset 0 size 4096 starting block 32475444)
[ 313.114692] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872598 (offset 0 size 4096 starting block 32475445)
[ 313.114697] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872599 (offset 0 size 4096 starting block 32475446)
[ 313.114701] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872600 (offset 0 size 4096 starting block 32475447)
[ 313.114705] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872601 (offset 0 size 4096 starting block 32475448)
[ 313.114709] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872602 (offset 0 size 4096 starting block 32475449)
[ 313.114714] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872603 (offset 0 size 4096 starting block 32475450)
[ 313.114718] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872604 (offset 0 size 4096 starting block 32475451)
[ 313.114722] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872605 (offset 0 size 4096 starting block 32475452)
[ 313.114727] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872606 (offset 0 size 4096 starting block 32475453)
[ 313.114731] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872607 (offset 0 size 4096 starting block 32475454)
[ 313.114736] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872608 (offset 0 size 4096 starting block 32475455)
[ 313.114740] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872609 (offset 0 size 20480 starting block 32475460)
[ 313.114747] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872610 (offset 0 size 4096 starting block 32475461)
[ 313.114751] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872611 (offset 0 size 4096 starting block 32475462)
[ 313.114756] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872612 (offset 0 size 4096 starting block 32475463)
[ 313.114762] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872613 (offset 0 size 40960 starting block 32475473)
[ 313.114773] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872615 (offset 0 size 57344 starting block 32475487)
[ 313.114787] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872616 (offset 0 size 57344 starting block 32475501)
[ 313.114799] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872617 (offset 0 size 77824 starting block 32475520)
[ 313.114817] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872618 (offset 0 size 57344 starting block 32475534)
[ 313.114832] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872619 (offset 0 size 73728 starting block 32475552)
[ 313.114849] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872620 (offset 0 size 172032 starting block 32475582)
[ 313.114871] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872620 (offset 0 size 172032 starting block 32475594)
[ 313.114882] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872621 (offset 0 size 4096 starting block 32475595)
[ 313.114887] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872622 (offset 0 size 4096 starting block 32475596)
[ 313.114891] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872623 (offset 0 size 4096 starting block 32475597)
[ 313.114896] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872624 (offset 0 size 4096 starting block 32475598)
[ 313.114900] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872625 (offset 0 size 4096 starting block 32475599)
[ 313.114905] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872626 (offset 0 size 4096 starting block 32475600)
[ 313.114909] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872627 (offset 0 size 4096 starting block 32475601)
[ 313.114913] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872628 (offset 0 size 4096 starting block 32475602)
[ 313.114918] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872629 (offset 0 size 4096 starting block 32475603)
[ 313.114922] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872630 (offset 0 size 4096 starting block 32475604)
[ 313.114926] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872631 (offset 0 size 4096 starting block 32475605)
[ 313.114931] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872632 (offset 0 size 4096 starting block 32475606)
[ 313.114935] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872633 (offset 0 size 4096 starting block 32475607)
[ 313.114939] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872634 (offset 0 size 4096 starting block 32475608)
[ 313.114944] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872635 (offset 0 size 4096 starting block 32475609)
[ 313.114948] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872636 (offset 0 size 4096 starting block 32475610)
[ 313.114953] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872637 (offset 0 size 4096 starting block 32475611)
[ 313.114957] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872638 (offset 0 size 4096 starting block 32475612)
[ 313.114964] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872639 (offset 0 size 4096 starting block 32475613)
[ 313.114969] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872640 (offset 0 size 4096 starting block 32475614)
[ 313.114973] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872641 (offset 0 size 4096 starting block 32475615)
[ 313.114978] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872642 (offset 0 size 4096 starting block 32475616)
[ 313.114982] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872643 (offset 0 size 4096 starting block 32475617)
[ 313.114986] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872644 (offset 0 size 4096 starting block 32475618)
[ 313.114991] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872645 (offset 0 size 4096 starting block 32475619)
[ 313.114996] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872646 (offset 0 size 4096 starting block 32475620)
[ 313.115000] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872647 (offset 0 size 4096 starting block 32475621)
[ 313.115004] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872649 (offset 0 size 4096 starting block 32475622)
[ 313.115008] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872648 (offset 0 size 8192 starting block 32475624)
[ 313.115014] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872650 (offset 0 size 4096 starting block 32475625)
[ 313.115018] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872652 (offset 0 size 4096 starting block 32475626)
[ 313.115023] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872653 (offset 0 size 4096 starting block 32475627)
[ 313.115027] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872654 (offset 0 size 4096 starting block 32475628)
[ 313.115031] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872651 (offset 0 size 16384 starting block 32475632)
[ 313.115038] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872655 (offset 0 size 4096 starting block 32475633)
[ 313.115042] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872657 (offset 0 size 4096 starting block 32475634)
[ 313.115046] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872656 (offset 0 size 8192 starting block 32475636)
[ 313.115051] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872658 (offset 0 size 20480 starting block 32475641)
[ 313.115058] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872659 (offset 0 size 4096 starting block 32475642)
[ 313.115065] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872660 (offset 0 size 12288 starting block 32475645)
[ 313.115070] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872661 (offset 0 size 4096 starting block 32475646)
[ 313.115075] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872662 (offset 0 size 4096 starting block 32475647)
[ 313.115079] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872663 (offset 0 size 4096 starting block 32475648)
[ 313.115086] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737528 (offset 0 size 4096 starting block 32480485)
[ 313.115091] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737529 (offset 0 size 4096 starting block 32480486)
[ 313.115096] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737530 (offset 0 size 4096 starting block 32480487)
[ 313.115100] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737531 (offset 0 size 4096 starting block 32480488)
[ 313.115105] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737532 (offset 0 size 4096 starting block 32480489)
[ 313.115109] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737533 (offset 0 size 4096 starting block 32480490)
[ 313.115113] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737534 (offset 0 size 4096 starting block 32480491)
[ 313.115118] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737535 (offset 0 size 4096 starting block 32480492)
[ 313.115122] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872452 (offset 0 size 4096 starting block 32480493)
[ 313.115127] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872479 (offset 0 size 4096 starting block 32480494)
[ 313.115131] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872496 (offset 0 size 4096 starting block 32480495)
[ 313.115136] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872500 (offset 0 size 4096 starting block 32480496)
[ 313.115141] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737606 (offset 0 size 61440 starting block 32480511)
[ 313.115154] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872555 (offset 0 size 4096 starting block 32480512)
[ 313.115159] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872819 (offset 0 size 4096 starting block 32480513)
[ 313.115164] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872820 (offset 0 size 4096 starting block 32480514)
[ 313.115171] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872821 (offset 0 size 4096 starting block 32480515)
[ 313.115176] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872822 (offset 0 size 4096 starting block 32480516)
[ 313.115180] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872823 (offset 0 size 4096 starting block 32480517)
[ 313.115185] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872824 (offset 0 size 4096 starting block 32480518)
[ 313.115189] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872825 (offset 0 size 4096 starting block 32480519)
[ 313.115193] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872826 (offset 0 size 4096 starting block 32480520)
[ 313.115198] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872827 (offset 0 size 4096 starting block 32480521)
[ 313.115202] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872828 (offset 0 size 4096 starting block 32480522)
[ 313.115207] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872829 (offset 0 size 4096 starting block 32480523)
[ 313.115211] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872830 (offset 0 size 4096 starting block 32480524)
[ 313.115215] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872831 (offset 0 size 4096 starting block 32480525)
[ 313.115223] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872832 (offset 0 size 155648 starting block 32480555)
[ 313.115244] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872832 (offset 0 size 155648 starting block 32480563)
[ 313.115252] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872833 (offset 0 size 20480 starting block 32480568)
[ 313.115259] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872834 (offset 0 size 4096 starting block 32480569)
[ 313.115263] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872835 (offset 0 size 4096 starting block 32480570)
[ 313.115268] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872836 (offset 0 size 4096 starting block 32480571)
[ 313.115272] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737623 (offset 0 size 4096 starting block 32480572)
[ 313.115277] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737620 (offset 0 size 16384 starting block 32480576)
[ 313.115283] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737621 (offset 0 size 12288 starting block 32480579)
[ 313.115292] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737625 (offset 0 size 4096 starting block 32480580)
[ 313.115296] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737622 (offset 0 size 16384 starting block 32480584)
[ 313.115303] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737624 (offset 0 size 20480 starting block 32480589)
[ 313.115311] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737627 (offset 0 size 4096 starting block 32480590)
[ 313.115315] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737626 (offset 0 size 8192 starting block 32480592)
[ 313.115321] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737628 (offset 0 size 49152 starting block 32480604)
[ 313.115332] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737629 (offset 0 size 4096 starting block 32480605)
[ 313.115339] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737630 (offset 0 size 53248 starting block 32480618)
[ 313.115351] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737632 (offset 0 size 4096 starting block 32480619)
[ 313.115355] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737633 (offset 0 size 36864 starting block 32480628)
[ 313.115364] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737634 (offset 0 size 8192 starting block 32480630)
[ 313.115370] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737636 (offset 0 size 8192 starting block 32480632)
[ 313.115377] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737637 (offset 0 size 24576 starting block 32480638)
[ 313.115385] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737638 (offset 0 size 8192 starting block 32480640)
[ 313.115390] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738124 (offset 0 size 4096 starting block 32480641)
[ 313.115395] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738125 (offset 0 size 4096 starting block 32480642)
[ 313.115399] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738126 (offset 0 size 4096 starting block 32480643)
[ 313.115404] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738127 (offset 0 size 36864 starting block 32480652)
[ 313.115413] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738128 (offset 0 size 4096 starting block 32480653)
[ 313.115417] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738129 (offset 0 size 4096 starting block 32480654)
[ 313.115421] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738130 (offset 0 size 4096 starting block 32480655)
[ 313.115425] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738131 (offset 0 size 4096 starting block 32480656)
[ 313.115430] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738132 (offset 0 size 4096 starting block 32480657)
[ 313.115434] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738133 (offset 0 size 4096 starting block 32480658)
[ 313.115438] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738134 (offset 0 size 4096 starting block 32480659)
[ 313.115443] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738135 (offset 0 size 4096 starting block 32480660)
[ 313.115449] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738136 (offset 0 size 28672 starting block 32480667)
[ 313.115456] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738137 (offset 0 size 4096 starting block 32480668)
[ 313.115460] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738138 (offset 0 size 4096 starting block 32480669)
[ 313.115465] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738139 (offset 0 size 12288 starting block 32480672)
[ 313.115470] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738140 (offset 0 size 4096 starting block 32480673)
[ 313.115474] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738141 (offset 0 size 4096 starting block 32480674)
[ 313.115479] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738142 (offset 0 size 4096 starting block 32480675)
[ 313.115483] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738145 (offset 0 size 4096 starting block 32480676)
[ 313.115488] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738143 (offset 0 size 8192 starting block 32480678)
[ 313.115493] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738144 (offset 0 size 36864 starting block 32480687)
[ 313.115501] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738146 (offset 0 size 4096 starting block 32480688)
[ 313.115506] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738147 (offset 0 size 4096 starting block 32480689)
[ 313.115510] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738148 (offset 0 size 4096 starting block 32480690)
[ 313.115517] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738149 (offset 0 size 4096 starting block 32480691)
[ 313.115521] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738151 (offset 0 size 4096 starting block 32480692)
[ 313.115526] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738150 (offset 0 size 8192 starting block 32480694)
[ 313.115531] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738152 (offset 0 size 8192 starting block 32480696)
[ 313.115536] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738153 (offset 0 size 4096 starting block 32480697)
[ 313.115540] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738154 (offset 0 size 4096 starting block 32480698)
[ 313.115544] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738155 (offset 0 size 4096 starting block 32480699)
[ 313.115548] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738156 (offset 0 size 4096 starting block 32480700)
[ 313.115552] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738157 (offset 0 size 4096 starting block 32480701)
[ 313.115556] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738158 (offset 0 size 4096 starting block 32480702)
[ 313.115560] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738159 (offset 0 size 4096 starting block 32480703)
[ 313.115565] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738160 (offset 0 size 4096 starting block 32480704)
[ 313.115568] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738161 (offset 0 size 4096 starting block 32480705)
[ 313.115572] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738162 (offset 0 size 4096 starting block 32480706)
[ 313.115576] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738163 (offset 0 size 4096 starting block 32480707)
[ 313.115581] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738164 (offset 0 size 49152 starting block 32480719)
[ 313.115591] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738166 (offset 0 size 4096 starting block 32480720)
[ 313.115597] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738167 (offset 0 size 4096 starting block 32480721)
[ 313.115602] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738168 (offset 0 size 4096 starting block 32480722)
[ 313.115606] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738169 (offset 0 size 4096 starting block 32480723)
[ 313.115611] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738171 (offset 0 size 4096 starting block 32480724)
[ 313.115615] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738172 (offset 0 size 4096 starting block 32480725)
[ 313.115619] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738173 (offset 0 size 4096 starting block 32480726)
[ 313.115623] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738174 (offset 0 size 4096 starting block 32480727)
[ 313.115627] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738175 (offset 0 size 4096 starting block 32480728)
[ 313.115631] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738176 (offset 0 size 4096 starting block 32480729)
[ 313.115635] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738177 (offset 0 size 4096 starting block 32480730)
[ 313.115639] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738178 (offset 0 size 8192 starting block 32480732)
[ 313.115644] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738179 (offset 0 size 4096 starting block 32480733)
[ 313.115649] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738180 (offset 0 size 4096 starting block 32480734)
[ 313.115653] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738181 (offset 0 size 4096 starting block 32480735)
[ 313.115657] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738182 (offset 0 size 4096 starting block 32480736)
[ 313.115661] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738183 (offset 0 size 4096 starting block 32480737)
[ 313.115666] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738184 (offset 0 size 4096 starting block 32480738)
[ 313.115670] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738185 (offset 0 size 4096 starting block 32480739)
[ 313.115674] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738186 (offset 0 size 4096 starting block 32480740)
[ 313.115679] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738187 (offset 0 size 4096 starting block 32480741)
[ 313.115683] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738188 (offset 0 size 4096 starting block 32480742)
[ 313.115687] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738189 (offset 0 size 8192 starting block 32480744)
[ 313.115692] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738190 (offset 0 size 4096 starting block 32480745)
[ 313.115696] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738191 (offset 0 size 4096 starting block 32480746)
[ 313.115700] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738192 (offset 0 size 4096 starting block 32480747)
[ 313.115704] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738194 (offset 0 size 4096 starting block 32480748)
[ 313.115709] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738193 (offset 0 size 8192 starting block 32480750)
[ 313.115716] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738195 (offset 0 size 4096 starting block 32480751)
[ 313.115721] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738196 (offset 0 size 12288 starting block 32480754)
[ 313.115727] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738197 (offset 0 size 4096 starting block 32480755)
[ 313.115731] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738198 (offset 0 size 4096 starting block 32480756)
[ 313.115735] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738199 (offset 0 size 4096 starting block 32480757)
[ 313.115740] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738201 (offset 0 size 4096 starting block 32480758)
[ 313.115744] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738200 (offset 0 size 8192 starting block 32480760)
[ 313.115750] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738202 (offset 0 size 4096 starting block 32480761)
[ 313.115754] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738203 (offset 0 size 4096 starting block 32480762)
[ 313.115758] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738204 (offset 0 size 4096 starting block 32480763)
[ 313.115762] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738205 (offset 0 size 4096 starting block 32480764)
[ 313.115766] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738206 (offset 0 size 4096 starting block 32480765)
[ 313.115770] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738207 (offset 0 size 4096 starting block 32480766)
[ 313.115775] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738208 (offset 0 size 4096 starting block 32480767)
[ 313.115779] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738209 (offset 0 size 4096 starting block 32480768)
[ 313.115786] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737600 (offset 0 size 200704 starting block 32480798)
[ 313.115812] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737600 (offset 0 size 200704 starting block 32480817)
[ 313.115830] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737601 (offset 0 size 225280 starting block 32480847)
[ 313.115855] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737601 (offset 0 size 225280 starting block 32480872)
[ 313.115879] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737602 (offset 0 size 98304 starting block 32480896)
[ 313.115900] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737605 (offset 0 size 208896 starting block 32481950)
[ 313.115924] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737605 (offset 0 size 208896 starting block 32481971)
[ 313.115943] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737607 (offset 0 size 110592 starting block 32481998)
[ 313.115963] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872554 (offset 0 size 8192 starting block 32482000)
[ 313.115971] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737608 (offset 0 size 65536 starting block 32482016)
[ 313.115986] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737609 (offset 0 size 86016 starting block 32482037)
[ 313.116004] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737615 (offset 0 size 245760 starting block 32482067)
[ 313.116028] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737615 (offset 0 size 245760 starting block 32482097)
[ 313.116051] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737616 (offset 0 size 12288 starting block 32482100)
[ 313.116058] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737617 (offset 0 size 12288 starting block 32482103)
[ 313.116064] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737618 (offset 0 size 53248 starting block 32482116)
[ 313.116078] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737619 (offset 0 size 122880 starting block 32482146)
[ 313.116101] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872567 (offset 0 size 4096 starting block 32482147)
[ 313.116109] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872569 (offset 0 size 49152 starting block 32482159)
[ 313.116121] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872571 (offset 0 size 36864 starting block 32482168)
[ 313.116130] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872577 (offset 0 size 4096 starting block 32482169)
[ 313.116135] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872578 (offset 0 size 4096 starting block 32482170)
[ 313.116139] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872579 (offset 0 size 4096 starting block 32482171)
[ 313.116143] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872580 (offset 0 size 4096 starting block 32482172)
[ 313.116148] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872581 (offset 0 size 4096 starting block 32482173)
[ 313.116152] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872582 (offset 0 size 4096 starting block 32482174)
[ 313.116156] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872583 (offset 0 size 8192 starting block 32482176)
[ 313.116164] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738399 (offset 0 size 4096 starting block 32483329)
[ 313.116169] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738400 (offset 0 size 4096 starting block 32483330)
[ 313.116174] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738401 (offset 0 size 4096 starting block 32483331)
[ 313.116178] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738402 (offset 0 size 4096 starting block 32483332)
[ 313.116182] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738403 (offset 0 size 4096 starting block 32483333)
[ 313.116187] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738404 (offset 0 size 4096 starting block 32483334)
[ 313.116191] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738405 (offset 0 size 4096 starting block 32483335)
[ 313.116195] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738406 (offset 0 size 4096 starting block 32483336)
[ 313.116200] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738407 (offset 0 size 4096 starting block 32483337)
[ 313.116204] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738408 (offset 0 size 4096 starting block 32483338)
[ 313.116208] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738409 (offset 0 size 4096 starting block 32483339)
[ 313.116213] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738410 (offset 0 size 4096 starting block 32483340)
[ 313.116217] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7738411 (offset 0 size 4096 starting block 32483341)
[ 313.116224] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737610 (offset 0 size 77824 starting block 32485907)
[ 313.116240] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737611 (offset 0 size 77824 starting block 32485926)
[ 313.116257] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737612 (offset 0 size 69632 starting block 32485943)
[ 313.116272] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737613 (offset 0 size 184320 starting block 32485973)
[ 313.116295] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737613 (offset 0 size 184320 starting block 32485988)
[ 313.116309] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737614 (offset 0 size 77824 starting block 32486007)
[ 313.116325] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872568 (offset 0 size 36864 starting block 32486016)
[ 313.116336] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737599 (offset 0 size 262144 starting block 32486046)
[ 313.116363] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737599 (offset 0 size 262144 starting block 32486076)
[ 313.116388] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737599 (offset 0 size 262144 starting block 32486080)
[ 313.116395] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737603 (offset 0 size 98304 starting block 32486104)
[ 313.116418] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7737604 (offset 0 size 114688 starting block 32486132)
[ 313.116441] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872570 (offset 0 size 8192 starting block 32486134)
[ 313.116448] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872576 (offset 0 size 8192 starting block 32486136)
[ 313.116455] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872687 (offset 0 size 12288 starting block 32487939)
[ 313.116464] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872688 (offset 0 size 4096 starting block 32487940)
[ 313.116469] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872689 (offset 0 size 4096 starting block 32487941)
[ 313.116473] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872690 (offset 0 size 4096 starting block 32487942)
[ 313.116478] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872691 (offset 0 size 4096 starting block 32487943)
[ 313.116482] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872693 (offset 0 size 4096 starting block 32487944)
[ 313.116486] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872694 (offset 0 size 4096 starting block 32487945)
[ 313.116490] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872695 (offset 0 size 4096 starting block 32487946)
[ 313.116495] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872696 (offset 0 size 4096 starting block 32487947)
[ 313.116500] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872697 (offset 0 size 4096 starting block 32487948)
[ 313.116504] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872698 (offset 0 size 4096 starting block 32487949)
[ 313.116509] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872699 (offset 0 size 4096 starting block 32487950)
[ 313.116513] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872700 (offset 0 size 4096 starting block 32487951)
[ 313.116517] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872701 (offset 0 size 4096 starting block 32487952)
[ 313.116521] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872702 (offset 0 size 4096 starting block 32487953)
[ 313.116525] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872703 (offset 0 size 4096 starting block 32487954)
[ 313.116530] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872704 (offset 0 size 4096 starting block 32487955)
[ 313.116534] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872705 (offset 0 size 4096 starting block 32487956)
[ 313.116538] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872706 (offset 0 size 4096 starting block 32487957)
[ 313.116543] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872707 (offset 0 size 4096 starting block 32487958)
[ 313.116547] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872708 (offset 0 size 4096 starting block 32487959)
[ 313.116551] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872709 (offset 0 size 4096 starting block 32487960)
[ 313.116556] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872710 (offset 0 size 4096 starting block 32487961)
[ 313.116560] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872711 (offset 0 size 4096 starting block 32487962)
[ 313.116564] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872712 (offset 0 size 4096 starting block 32487963)
[ 313.116568] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872713 (offset 0 size 4096 starting block 32487964)
[ 313.116572] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872714 (offset 0 size 4096 starting block 32487965)
[ 313.116576] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872715 (offset 0 size 4096 starting block 32487966)
[ 313.116582] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872716 (offset 0 size 4096 starting block 32487967)
[ 313.116586] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872717 (offset 0 size 4096 starting block 32487968)
[ 313.116591] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872718 (offset 0 size 4096 starting block 32487969)
[ 313.116595] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872719 (offset 0 size 4096 starting block 32487970)
[ 313.116600] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872720 (offset 0 size 4096 starting block 32487971)
[ 313.116604] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872721 (offset 0 size 4096 starting block 32487972)
[ 313.116608] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872722 (offset 0 size 4096 starting block 32487973)
[ 313.116613] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872723 (offset 0 size 4096 starting block 32487974)
[ 313.116617] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872724 (offset 0 size 4096 starting block 32487975)
[ 313.116621] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872725 (offset 0 size 4096 starting block 32487976)
[ 313.116626] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872726 (offset 0 size 4096 starting block 32487977)
[ 313.116630] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872727 (offset 0 size 4096 starting block 32487978)
[ 313.116634] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872728 (offset 0 size 4096 starting block 32487979)
[ 313.116639] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872729 (offset 0 size 4096 starting block 32487980)
[ 313.116643] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872730 (offset 0 size 4096 starting block 32487981)
[ 313.116647] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872731 (offset 0 size 4096 starting block 32487982)
[ 313.116651] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872732 (offset 0 size 4096 starting block 32487983)
[ 313.116656] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872733 (offset 0 size 4096 starting block 32487984)
[ 313.116660] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872734 (offset 0 size 4096 starting block 32487985)
[ 313.116664] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872735 (offset 0 size 4096 starting block 32487986)
[ 313.116669] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872736 (offset 0 size 4096 starting block 32487987)
[ 313.116674] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872738 (offset 0 size 4096 starting block 32487988)
[ 313.116679] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872739 (offset 0 size 4096 starting block 32487989)
[ 313.116683] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872740 (offset 0 size 4096 starting block 32487990)
[ 313.116688] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872742 (offset 0 size 4096 starting block 32487991)
[ 313.116692] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872743 (offset 0 size 4096 starting block 32487992)
[ 313.116697] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872744 (offset 0 size 8192 starting block 32487994)
[ 313.116702] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872745 (offset 0 size 4096 starting block 32487995)
[ 313.116706] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872746 (offset 0 size 4096 starting block 32487996)
[ 313.116713] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872747 (offset 0 size 4096 starting block 32487997)
[ 313.116718] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872748 (offset 0 size 4096 starting block 32487998)
[ 313.116722] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872749 (offset 0 size 4096 starting block 32487999)
[ 313.116726] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872752 (offset 0 size 4096 starting block 32488000)
[ 313.116731] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872774 (offset 0 size 4096 starting block 32488001)
[ 313.116736] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872775 (offset 0 size 4096 starting block 32488002)
[ 313.116740] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872776 (offset 0 size 4096 starting block 32488003)
[ 313.116745] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872777 (offset 0 size 4096 starting block 32488004)
[ 313.116749] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872778 (offset 0 size 4096 starting block 32488005)
[ 313.116754] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872779 (offset 0 size 4096 starting block 32488006)
[ 313.116759] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872780 (offset 0 size 4096 starting block 32488007)
[ 313.116763] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872781 (offset 0 size 4096 starting block 32488008)
[ 313.116767] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872782 (offset 0 size 8192 starting block 32488010)
[ 313.116772] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872783 (offset 0 size 4096 starting block 32488011)
[ 313.116777] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872784 (offset 0 size 4096 starting block 32488012)
[ 313.116781] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872785 (offset 0 size 4096 starting block 32488013)
[ 313.116785] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872786 (offset 0 size 4096 starting block 32488014)
[ 313.116790] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872787 (offset 0 size 4096 starting block 32488015)
[ 313.116794] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872788 (offset 0 size 4096 starting block 32488016)
[ 313.116798] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872790 (offset 0 size 4096 starting block 32488017)
[ 313.116803] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872791 (offset 0 size 4096 starting block 32488018)
[ 313.116807] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872792 (offset 0 size 4096 starting block 32488019)
[ 313.116811] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872793 (offset 0 size 4096 starting block 32488020)
[ 313.116815] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872794 (offset 0 size 4096 starting block 32488021)
[ 313.116820] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872795 (offset 0 size 4096 starting block 32488022)
[ 313.116824] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872796 (offset 0 size 4096 starting block 32488023)
[ 313.116828] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872797 (offset 0 size 4096 starting block 32488024)
[ 313.116832] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872798 (offset 0 size 4096 starting block 32488025)
[ 313.116837] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872801 (offset 0 size 4096 starting block 32488026)
[ 313.116845] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872799 (offset 0 size 8192 starting block 32488028)
[ 313.116850] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872802 (offset 0 size 4096 starting block 32488029)
[ 313.116855] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872804 (offset 0 size 4096 starting block 32488030)
[ 313.116859] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872803 (offset 0 size 8192 starting block 32488032)
[ 313.116864] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872805 (offset 0 size 4096 starting block 32488033)
[ 313.116869] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872806 (offset 0 size 4096 starting block 32488034)
[ 313.116874] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872807 (offset 0 size 12288 starting block 32488037)
[ 313.116880] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872808 (offset 0 size 4096 starting block 32488038)
[ 313.116885] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872809 (offset 0 size 4096 starting block 32488039)
[ 313.116889] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872810 (offset 0 size 4096 starting block 32488040)
[ 313.116894] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872811 (offset 0 size 40960 starting block 32488050)
[ 313.116903] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872812 (offset 0 size 20480 starting block 32488055)
[ 313.116912] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872813 (offset 0 size 12288 starting block 32488058)
[ 313.116918] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872814 (offset 0 size 4096 starting block 32488059)
[ 313.116922] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872816 (offset 0 size 4096 starting block 32488060)
[ 313.116927] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872815 (offset 0 size 8192 starting block 32488062)
[ 313.116932] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872817 (offset 0 size 4096 starting block 32488063)
[ 313.116936] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872818 (offset 0 size 4096 starting block 32488064)
[ 313.116942] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872665 (offset 0 size 12288 starting block 32488067)
[ 313.116949] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872666 (offset 0 size 4096 starting block 32488068)
[ 313.116954] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872667 (offset 0 size 4096 starting block 32488069)
[ 313.116959] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872669 (offset 0 size 4096 starting block 32488070)
[ 313.116963] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872668 (offset 0 size 8192 starting block 32488072)
[ 313.116968] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872670 (offset 0 size 12288 starting block 32488075)
[ 313.116974] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872673 (offset 0 size 4096 starting block 32488076)
[ 313.116979] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872671 (offset 0 size 16384 starting block 32488080)
[ 313.116985] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872674 (offset 0 size 4096 starting block 32488081)
[ 313.116989] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872675 (offset 0 size 4096 starting block 32488082)
[ 313.116994] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872676 (offset 0 size 12288 starting block 32488085)
[ 313.116999] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872677 (offset 0 size 20480 starting block 32488090)
[ 313.117009] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872678 (offset 0 size 57344 starting block 32488104)
[ 313.117021] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872679 (offset 0 size 49152 starting block 32488116)
[ 313.117031] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872680 (offset 0 size 12288 starting block 32488119)
[ 313.117039] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872681 (offset 0 size 20480 starting block 32488124)
[ 313.117045] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872682 (offset 0 size 4096 starting block 32488125)
[ 313.117051] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872683 (offset 0 size 12288 starting block 32488128)
[ 313.117057] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872685 (offset 0 size 4096 starting block 32488129)
[ 313.117061] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872755 (offset 0 size 4096 starting block 32488130)
[ 313.117066] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872686 (offset 0 size 8192 starting block 32488132)
[ 313.117071] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872692 (offset 0 size 8192 starting block 32488134)
[ 313.117076] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872737 (offset 0 size 8192 starting block 32488136)
[ 313.117081] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872750 (offset 0 size 8192 starting block 32488138)
[ 313.117086] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872751 (offset 0 size 8192 starting block 32488140)
[ 313.117091] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 7872753 (offset 0 size 8192 starting block 32488142)
[ 313.117096] EXT4-fs warning (device sdb1): ext4_end_bio:316: I/O error writing to inode 787275 -
Is there a way to turn off an echo on the serial port?
I am sending some commands to the serial and they get echoed back before I can read a reply. Sending the same commands via Socket doesn't give me an echo, so my algorithm for Serial and TCP/IP connection has to differ. It would be nice, however, to just turn off the echo.
Any ideas?
Thanks!
Janny.I am not connecting through a modem but doing a direct serial connection from PC to a telecom equipment serial port. IF I disable an echo using ATE modem command the equipment I sent the commands to freaks out since it can't recognize the command.
Maybe you are looking for
-
Dear Gurus In which table can we get the open production order quantities and the gr dates. Regards Sandip Sarkar
-
Difference between G/L Balance and Inventory Audit Report
Hi All, while checking the G/L ledger for Inventory account and the Inventory Audit report, there is a difference between the amounts posted. The closing balance till 31/03/09 is fine but afterwards the balance is not matchin at all. I hav tr
-
Sort alphabetically a lookup column in 'Quick edit'
Hi Everyone, I've had this problem for a long time now and have not been able to get it working. I have a List with several fields, one of them is a Drop-down list with a lookup field linked to another list called 'Customers' which has two fields 'ID
-
I am using an alternate monitor. Can I turn off the laptop monitor and still operate normally?
I am using an alternate monitor with my MacBook Pro. Is there a way to disable the laptop monitor so that the laptop can be closed?
-
Forgot passcode lock on iphone 5
forgot passcode lock how do I access it?