As soon as I try using my USB external harddrive, luksEncrypted under btrfs, after a few seconds, backuping files crashes with the following logs: [16270.036109] ------------[ cut here ]------------ [16270.036117] WARNING: CPU: 1 PID: 19367 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x50/0x110() [16270.036119] BTRFS: Transaction aborted (error -5) [16270.036121] Modules linked in: fuse xfs dm_crypt xts gf128mul algif_skcipher af_alg af_packet lm63 msr dm_mirror dm_region_hash dm_log dm_mod nvidia(PO) gspca_sn9c20x gspca_main videodev media coretemp kvm drm microcode ppdev iTCO_wdt iTCO_vendor_support serio_raw i2c_i801 snd_hda_codec_analog snd_hda_codec_generic snd_cmipci r8169 snd_mpu401_uart lpc_ich mii snd_opl3_lib snd_hda_codec_hdmi snd_rawmidi rng_core snd_seq_dummy snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd shpchp parport_pc parport ns558 soundcore asus_atk0110 gameport floppy firewire_sbp2 firewire_core crc_itu_t cpufreq_ondemand cpufreq_conservative cpufreq_powersave acpi_cpufreq processor evdev ipv6 autofs4 hid_generic [16270.036195] usbhid hid uas usb_storage uhci_hcd ehci_pci ehci_hcd usbcore sr_mod ata_generic pata_acpi usb_common button ide_generic piix ide_pci_generic ide_core ata_piix [16270.036216] CPU: 1 PID: 19367 Comm: btrfs-transacti Tainted: P O 3.17.0-desktop-0.rc7.1.mga5 #1 [16270.036218] Hardware name: stem manufacturer System Product Name/P5LD2-SE, BIOS 1003 04/12/2007 [16270.036221] 0000000000000009 ffff88009c50fcc0 ffffffff8168f18c ffff88009c50fd08 [16270.036226] ffff88009c50fcf8 ffffffff81069b3d 00000000fffffffb ffff8800a883bbe0 [16270.036230] ffff88009a516800 ffffffff81853530 0000000000000623 ffff88009c50fd58 [16270.036235] Call Trace: [16270.036242] [<ffffffff8168f18c>] dump_stack+0x45/0x56 [16270.036248] [<ffffffff81069b3d>] warn_slowpath_common+0x7d/0xa0 [16270.036252] [<ffffffff81069bac>] warn_slowpath_fmt+0x4c/0x50 [16270.036256] [<ffffffff81295cd0>] __btrfs_abort_transaction+0x50/0x110 [16270.036262] [<ffffffff812c249e>] cleanup_transaction+0x6e/0x2b0 [16270.036267] [<ffffffff810a4c40>] ? __wake_up_sync+0x20/0x20 [16270.036271] [<ffffffff812c33f9>] btrfs_commit_transaction+0x6e9/0x960 [16270.036275] [<ffffffff812bee75>] transaction_kthread+0x245/0x260 [16270.036280] [<ffffffff812bec30>] ? btrfs_cleanup_transaction+0x540/0x540 [16270.036285] [<ffffffff81086b6b>] kthread+0xdb/0x100 [16270.036289] [<ffffffff81086a90>] ? kthread_create_on_node+0x180/0x180 [16270.036294] [<ffffffff8169643c>] ret_from_fork+0x7c/0xb0 [16270.036298] [<ffffffff81086a90>] ? kthread_create_on_node+0x180/0x180 [16270.036301] ---[ end trace fb98ffa84671c534 ]--- [16270.036305] BTRFS: error (device dm-2) in cleanup_transaction:1571: errno=-5 IO failure [16270.036308] BTRFS info (device dm-2): delayed_refs has NO entry Looks related to btrfs rather than the encryption; that thing used to work under mga4 (I'll update the bug report with more tests). Cheers, Chris. --- Reproducible: Steps to Reproduce:
Can you reporoduce it without using the proprietary nvidia driver ?
CC: (none) => tmb
Here you go, replaced nvidia with nouveau driver and last kernel. I'll test on other system to be sure that's not hardware related. --------------- [ 161.097829] BTRFS: device fsid 6bc9e297-88ec-45b5-bc31-421d513e7251 devid 1 transid 83 /dev/dm-2 [ 161.171666] BTRFS info (device dm-2): disk space caching is enabled [ 209.441631] end_request: critical target error, dev sdd, sector 0 [ 209.441648] BTRFS: bdev /dev/mapper/_dev_sdd1 errs: wr 0, rd 0, flush 1, corrupt 0, gen 0 [ 209.441655] BTRFS: error (device dm-2) in write_all_supers:3442: errno=-5 IO failure (errors while submitting device barriers.) [ 209.441659] BTRFS info (device dm-2): forced readonly [ 209.441663] BTRFS warning (device dm-2): Skipping commit of aborted transaction. [ 209.441665] ------------[ cut here ]------------ [ 209.441674] WARNING: CPU: 1 PID: 2530 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x50/0x110() [ 209.441676] BTRFS: Transaction aborted (error -5) [ 209.441678] Modules linked in: fuse xfs dm_crypt xts gf128mul algif_skcipher af_alg af_packet lm63 msr dm_zero dm_mirror dm_region_hash dm_log dm_mod nouveau gspca_sn9c20x gspca_main mxm_wmi videodev wmi video ttm media drm_kms_helper drm i2c_algo_bit ppdev coretemp kvm iTCO_wdt iTCO_vendor_support snd_hda_codec_analog snd_hda_codec_generic microcode serio_raw snd_hda_codec_hdmi snd_hda_intel snd_hda_controller i2c_i801 snd_cmipci snd_hda_codec snd_mpu401_uart snd_opl3_lib lpc_ich rng_core snd_hwdep snd_seq_dummy snd_rawmidi r8169 mii parport_pc parport shpchp snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd ns558 gameport soundcore asus_atk0110 floppy firewire_sbp2 firewire_core crc_itu_t cpufreq_ondemand cpufreq_conservative cpufreq_powersave [ 209.441751] acpi_cpufreq processor evdev ipv6 autofs4 hid_generic usbhid hid uas usb_storage uhci_hcd ehci_pci ehci_hcd sr_mod ata_generic pata_acpi usbcore usb_common button ide_generic piix ide_pci_generic ide_core ata_piix [ 209.441777] CPU: 1 PID: 2530 Comm: btrfs-transacti Not tainted 3.17.0-desktop-0.rc7.2.mga5 #1 [ 209.441780] Hardware name: stem manufacturer System Product Name/P5LD2-SE, BIOS 1003 04/12/2007 [ 209.441782] 0000000000000009 ffff8800b8f8bcc0 ffffffff8168f19c ffff8800b8f8bd08 [ 209.441787] ffff8800b8f8bcf8 ffffffff81069b2d 00000000fffffffb ffff88009b2b8460 [ 209.441792] ffff8800b02ec800 ffffffff81853530 0000000000000623 ffff8800b8f8bd58 [ 209.441796] Call Trace: [ 209.441804] [<ffffffff8168f19c>] dump_stack+0x45/0x56 [ 209.441809] [<ffffffff81069b2d>] warn_slowpath_common+0x7d/0xa0 [ 209.441813] [<ffffffff81069b9c>] warn_slowpath_fmt+0x4c/0x50 [ 209.441817] [<ffffffff81295ce0>] __btrfs_abort_transaction+0x50/0x110 [ 209.441823] [<ffffffff812c24ae>] cleanup_transaction+0x6e/0x2b0 [ 209.441828] [<ffffffff810a4c30>] ? __wake_up_sync+0x20/0x20 [ 209.441833] [<ffffffff812c3409>] btrfs_commit_transaction+0x6e9/0x960 [ 209.441837] [<ffffffff812bee85>] transaction_kthread+0x245/0x260 [ 209.441841] [<ffffffff812bec40>] ? btrfs_cleanup_transaction+0x540/0x540 [ 209.441847] [<ffffffff81086b5b>] kthread+0xdb/0x100 [ 209.441851] [<ffffffff81086a80>] ? kthread_create_on_node+0x180/0x180 [ 209.441855] [<ffffffff8169643c>] ret_from_fork+0x7c/0xb0 [ 209.441860] [<ffffffff81086a80>] ? kthread_create_on_node+0x180/0x180 [ 209.441863] ---[ end trace 1239b41e9a78d2c2 ]--- [ 209.441866] BTRFS: error (device dm-2) in cleanup_transaction:1571: errno=-5 IO failure [ 209.441870] BTRFS info (device dm-2): delayed_refs has NO entry
I confirm this is *not* a hardware issue for the following reason: 1) I have tested the same drive with mga4 and kernel-3.12.26-tmp-laptop-1.mga4 and it works perfectly fine even under heavy loads. 2) Interestingly enough, I get the same kernel trace on mga4 using the desktop-kernel 3.14.18-desktop-3.mga4; so it seems the bug has been introduced already in 3.14.18. ------- I did another test by plugging another external USB hard drive of the same kind, which is on xfs filesystem, and as soon as I try to copy on it I get I/O errors as well! Both of these drives are quite old; they are respectively Maxtor One Touch II and One Touch I External harddrives and I suspect that the reason of failing might be a wrong setting within USB123 bandwidth. For (working) kernel-tmb the loaded modules around usbcore are usbcore usb_storage,ehci_hdc,ehci_pci,xhci_hcd usb_common
sorry, I pressed enter too early....:) Now for the non-working kernel-desktop, on mga4 I get the same usbcore usb_storage, ehci_hcd,ehci_pci,xhci_hcd and on current cauldron 3.17.0-desktop-3.mga5 I get usbcore uas,uhci_hcd,usb_storage,echi_hcd,ehci_pci,usbhid Please, let me know if you need additional infos.
Target Milestone: --- => Mageia 5Severity: normal => major
I've just pushed a kernel-3.17.0-5.mga5 to the buildsystem can you test it when it's available...
Done, unfortunately I get the same behaviour and trace: ---- [ 203.185536] BTRFS: error (device dm-2) in write_all_supers:3442: errno=-5 IO failure (errors while submitting device barriers.) [ 203.185540] BTRFS info (device dm-2): forced readonly [ 203.185543] BTRFS warning (device dm-2): Skipping commit of aborted transaction. [ 203.185546] ------------[ cut here ]------------ [ 203.185554] WARNING: CPU: 0 PID: 2340 at fs/btrfs/super.c:259 __btrfs_abort_transaction+0x50/0x110() [ 203.185556] BTRFS: Transaction aborted (error -5) [ 203.185558] Modules linked in: iptable_filter ip_tables x_tables xfs dm_crypt xts gf128mul algif_skcipher af_alg af_packet lm63 msr nvidia(PO) coretemp kvm gspca_sn9c20x gspca_main videodev media hid_generic iTCO_wdt iTCO_vendor_support snd_hda_codec_analog snd_hda_codec_generic ppdev snd_hda_codec_hdmi microcode serio_raw snd_hda_intel drm snd_seq_midi snd_hda_controller snd_hda_codec usbhid snd_seq_dummy snd_seq_oss hid snd_cmipci snd_mpu401_uart snd_opl3_lib snd_hwdep snd_seq_midi_event snd_seq i2c_i801 snd_rawmidi snd_seq_device lpc_ich snd_pcm_oss snd_mixer_oss snd_pcm parport_pc parport rng_core snd_timer snd r8169 mii soundcore dm_mirror dm_region_hash dm_log shpchp ns558 gameport dm_mod asus_atk0110 floppy cpufreq_ondemand cpufreq_conservative cpufreq_powersave acpi_cpufreq processor evdev [ 203.185636] ipv6 autofs4 uas usb_storage uhci_hcd ehci_pci sr_mod ata_generic pata_acpi ehci_hcd usbcore usb_common button ide_generic piix ide_pci_generic ide_core ata_piix [ 203.185650] CPU: 0 PID: 2340 Comm: btrfs-transacti Tainted: P O 3.17.0-desktop-5.mga5 #1 [ 203.185652] Hardware name: stem manufacturer System Product Name/P5LD2-SE, BIOS 1003 04/12/2007 [ 203.185653] 0000000000000009 ffff8800aaf93cc0 ffffffff8168f23c ffff8800aaf93d08 [ 203.185657] ffff8800aaf93cf8 ffffffff81069b2d 00000000fffffffb ffff88008282d0a0 [ 203.185659] ffff8800aac0f800 ffffffff81853530 0000000000000623 ffff8800aaf93d58 [ 203.185662] Call Trace: [ 203.185668] [<ffffffff8168f23c>] dump_stack+0x45/0x56 [ 203.185672] [<ffffffff81069b2d>] warn_slowpath_common+0x7d/0xa0 [ 203.185674] [<ffffffff81069b9c>] warn_slowpath_fmt+0x4c/0x50 [ 203.185677] [<ffffffff81295d80>] __btrfs_abort_transaction+0x50/0x110 [ 203.185681] [<ffffffff812c254e>] cleanup_transaction+0x6e/0x2b0 [ 203.185685] [<ffffffff810a4c30>] ? __wake_up_sync+0x20/0x20 [ 203.185688] [<ffffffff812c34a9>] btrfs_commit_transaction+0x6e9/0x960 [ 203.185691] [<ffffffff812bef25>] transaction_kthread+0x245/0x260 [ 203.185694] [<ffffffff812bece0>] ? btrfs_cleanup_transaction+0x540/0x540 [ 203.185697] [<ffffffff81086b5b>] kthread+0xdb/0x100 [ 203.185700] [<ffffffff81086a80>] ? kthread_create_on_node+0x180/0x180 [ 203.185704] [<ffffffff816964bc>] ret_from_fork+0x7c/0xb0 [ 203.185706] [<ffffffff81086a80>] ? kthread_create_on_node+0x180/0x180 [ 203.185708] ---[ end trace c7f44b9fd66b541c ]--- [ 203.185711] BTRFS: error (device dm-2) in cleanup_transaction:1571: errno=-5 IO failure [ 203.185713] BTRFS info (device dm-2): delayed_refs has NO entry
The hardware: snd_hda_intel : NVIDIA Corporation|GK107 HDMI Audio Controller [MULTIMEDIA_AUDIO_DEV] (rev: a1) Card:NVIDIA GeForce 400 series and later: NVIDIA Corporation|GK107 [GeForce GTX 650] [DISPLAY_VGA] (rev: a1) r8169 : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (rev: 01) snd_cmipci : C-Media Electronics Inc|CMI8738/CMI8768 PCI Audio [MULTIMEDIA_AUDIO] (rev: 10) r8169 : D-Link System Inc|DGE-528T Gigabit Ethernet Adapter [NETWORK_ETHERNET] (rev: 10) i2c_i801 : Intel Corporation|NM10/ICH7 Family SMBus Controller [SERIAL_SMBUS] (rev: 01) ata_piix : Intel Corporation|NM10/ICH7 Family SATA Controller [IDE mode] [STORAGE_IDE] (rev: 01) ata_piix : Intel Corporation|82801G (ICH7 Family) IDE Controller [STORAGE_IDE] (rev: 01) intel_rng : Intel Corporation|82801GB/GR (ICH7 Family) LPC Interface Bridge [BRIDGE_ISA] (rev: 01) unknown : Intel Corporation|82801 PCI Bridge [BRIDGE_PCI] (rev: e1) ehci_pci : Intel Corporation|NM10/ICH7 Family USB2 EHCI Controller [SERIAL_USB] (rev: 01) uhci_hcd : Intel Corporation|NM10/ICH7 Family USB UHCI Controller #4 [SERIAL_USB] (rev: 01) uhci_hcd : Intel Corporation|NM10/ICH7 Family USB UHCI Controller #3 [SERIAL_USB] (rev: 01) uhci_hcd : Intel Corporation|NM10/ICH7 Family USB UHCI Controller #2 [SERIAL_USB] (rev: 01) uhci_hcd : Intel Corporation|NM10/ICH7 Family USB UHCI Controller #1 [SERIAL_USB] (rev: 01) shpchp : Intel Corporation|NM10/ICH7 Family PCI Express Port 4 [BRIDGE_PCI] (rev: 01) shpchp : Intel Corporation|NM10/ICH7 Family PCI Express Port 1 [BRIDGE_PCI] (rev: 01) snd_hda_intel : Intel Corporation|NM10/ICH7 Family High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (rev: 01) shpchp : Intel Corporation|82945G/GZ/P/PL PCI Express Root Port [BRIDGE_PCI] (rev: 02) unknown : Intel Corporation|82945G/GZ/P/PL Memory Controller Hub [BRIDGE_HOST] (rev: 02) hub : Linux 3.17.0-desktop-5.mga5 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] hub : Linux 3.17.0-desktop-5.mga5 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] hub : Linux 3.17.0-desktop-5.mga5 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] usbhid : Logitech|USB Gaming Mouse [Human Interface Device|Boot Interface Subclass|Mouse] usbhid : Logitech|USB-PS/2 Optical Mouse [Human Interface Device|Boot Interface Subclass|Mouse] hub : Linux 3.17.0-desktop-5.mga5 uhci_hcd|UHCI Host Controller [Hub|Unused|Full speed (or root) hub] hub : Linux 3.17.0-desktop-5.mga5 ehci_hcd|EHCI Host Controller [Hub|Unused|Full speed (or root) hub] gspca_sn9c20x : Microdia|USB20 Camera usb_storage : Maxtor|OneTouch II [Mass Storage|SCSI|Bulk-Only] hid_generic : Logitech USB Gaming Mouse hid_generic : Logitech USB Gaming Mouse hid_generic : Logitech USB-PS/2 Optical Mouse
Confirmed also with 3.17.2-desktop-3.mga5; on a completely different hardware with the disks plugged into usb2 ports.
Ok, so it follows the usb disk, not the computer. 2 things... test 3.17.2-desktop-4.mga5, it has several usb storage fixes. Can you also provide lspcidrake -v (the "-v" part is to see ids) and lsusb output when the troublesome usb disks are connected The btrfs trace is only a result, not the real bug. i/o to the disc/enclosure breaks down and takes the fs with it. We have several quirks for borked usb storage, so I guess theese disks might also need some...
Created attachment 5588 [details] syslog when plugging the usb driver
Created attachment 5589 [details] output of lspcidrake -v
Created attachment 5590 [details] output of lsusb
Here you go; same crashes with 3.17.2-desktop-4.mga5. Here I have used my second "onetouch" external usb harddrive, over XFS, which yields to the same issue. These drives have also firewire plugs and they do work fine; that's really something wrong with their usb talking indeed! Thanks, cheers.
Summary: kernel trace in btrfs => kernel trace + I/O error for external USB harddrives (Maxtor Onetouch)
I am getting exactely the same I/O error using another external USB harddrive, from a different manufacturer and on another hardware (and last kernel 3.18.1-desktop). So this starts to be weird, either all quirks have been removed or there is something wrong with the "new" kernel USB management. In fact, all these external hardrives shares the common feature to have a IDE harddrive inside the box. The new tested external usb drive is: new high-speed USB device number 9 using ehci-pci [ 528.074526] usb 1-1.1: New USB device found, idVendor=152d, idProduct=2338 [ 528.074528] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 528.074529] usb 1-1.1: Product: USB to ATA/ATAPI bridge [ 528.074530] usb 1-1.1: Manufacturer: JMicron [ 528.074531] usb 1-1.1: SerialNumber: 7D3200AA4B50 [ 528.075304] usb-storage 1-1.1:1.0: USB Mass Storage device detected [ 528.075561] scsi host9: usb-storage 1-1.1:1.0 [ 529.077843] scsi 9:0:0:0: Direct-Access WDC WD32 00AAJB-00J3A0 PQ: 0 ANSI: 2 CCS [ 529.078306] sd 9:0:0:0: Attached scsi generic sg2 type 0 [ 529.078488] sd 9:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB) [ 529.079508] sd 9:0:0:0: [sdb] Write Protect is off [ 529.079519] sd 9:0:0:0: [sdb] Mode Sense: 28 00 00 00 [ 529.080501] sd 9:0:0:0: [sdb] No Caching mode page found [ 529.080504] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Could you try a real fs like ext4... that would help rule out kernel/usb_storage issues. Btw, I think you are brave... I wouldn't trust btrfs with anything important. The amount of data corruption fixes landing all over btrfs all the time makes me think it will never be something that should be recommended.
OK :) I'll try with ext4; but test on comment 13 (my second maxtor onetouch disk) and the other test on comment 14 (another drive on another machine) were done with XFS. If that matters, the two maxtor drives (the one having btrfs and the one having xfs) also have a firewire port in addition to the usb port. Since that bug appeared, I have been actually using the firewire port without any pb suggesting that the drives and their fs are working fine. PS: For the braveness, no so much, I am backuping on the 2 drives at same time in case btrfs would fail (but so far, so good).
Ah, I missed the one tested with xfs :/ Can you show the trace on that one too
Here you go, tested on freshly formatted ext4! Plugging the *USB* port: [ 509.076245] usb 1-1.3: new high-speed USB device number 5 using ehci-pci [ 509.161998] usb 1-1.3: New USB device found, idVendor=0d49, idProduct=7100 [ 509.162004] usb 1-1.3: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [ 509.162007] usb 1-1.3: Product: OneTouch II [ 509.162009] usb 1-1.3: Manufacturer: Maxtor [ 509.162011] usb 1-1.3: SerialNumber: H80HH96H [ 509.162295] usb-storage 1-1.3:1.0: USB Mass Storage device detected [ 509.162552] scsi host18: usb-storage 1-1.3:1.0 [ 510.218282] scsi 18:0:0:0: Direct-Access Maxtor OneTouch II 0244 PQ: 0 ANSI: 4 The first errors are during partionning and formatting: [ 229.952553] blk_update_request: critical target error, dev sdj, sector 0 [ 230.337346] blk_update_request: critical target error, dev sdj, sector 0 [ 230.486466] blk_update_request: critical target error, dev sdj, sector 0 [ 230.671741] blk_update_request: critical target error, dev sdj, sector 0 [ 238.064529] sdj: sdj1 [ 238.234798] sdj: sdj1 [ 238.405077] sdj: sdj1 [ 238.574788] sdj: sdj1 [ 238.744063] sdj: sdj1 [ 238.914460] sdj: sdj1 [ 239.085210] sdj: sdj1 [ 239.256224] sdj: sdj1 [ 239.426731] sdj: sdj1 [ 239.597355] sdj: sdj1 Then, I insist and I can mount the disk, and attempt a copy on it: [ 266.870095] EXT4-fs (sdj1): mounted filesystem with ordered data mode. Opts: (null) [ 267.586220] blk_update_request: critical target error, dev sdj, sector 0 [ 272.944259] blk_update_request: critical target error, dev sdj, sector 486803480 [ 272.944294] Aborting journal on device sdj1-8. [ 273.077122] EXT4-fs error (device sdj1): ext4_journal_check_start:56: Detected aborted journal [ 273.077128] EXT4-fs (sdj1): Remounting filesystem read-only Game Over :-/ ------- Now I unplug the usb cable, and plug the firewire port: [ 719.395966] scsi host20: SBP-2 IEEE-1394 [ 719.396056] firewire_core 0000:0d:00.0: created device fw1: GUID 0010b92100704d91, S400 [ 719.396062] firewire_core 0000:0d:00.0: phy config: new root=ffc0, gap_count=5 [ 719.921006] firewire_sbp2 fw1.1: logged in to LUN 0000 (0 retries) [ 719.922409] scsi 20:0:0:0: Direct-Access Maxtor OneTouch II 0244 PQ: 0 ANSI: 4 [ 719.933683] sd 20:0:0:0: [sdj] 976773168 512-byte logical blocks: (500 GB/465 GiB) [ 719.934140] sd 20:0:0:0: [sdj] Write Protect is off [ 719.934146] sd 20:0:0:0: [sdj] Mode Sense: 2f 00 00 00 [ 719.934312] sd 20:0:0:0: [sdj] Cache data unavailable [ 719.934317] sd 20:0:0:0: [sdj] Assuming drive cache: write through [ 719.980609] sdj: sdj1 [ 719.983227] sd 20:0:0:0: [sdj] Attached SCSI disk and start again from scratch. No error during formatting in ext4, I can mount the drive without error and copy files with heavy loads; 50MB/s no issue.
Assignee: bugsquad => tmbWhiteboard: (none) => MGA5TOO
Can you check if you are affected by this uas (USB attached SCSI) module issue, was reported via https://forums.mageia.org/en/viewtopic.php?f=41&t=9835 and more recently as https://forums.mageia.org/en/viewtopic.php?f=7&t=9933 Also at Arch via https://bbs.archlinux.org/viewtopic.php?id=183190 Might be a long shot but still worth a try ...
CC: (none) => doktor5000
Ahhhh, apparently this has been fixed somehow in the subsequent kernel releases; just tested with: 4.1.8-desktop-1.mga5 and one of the drives mentioned above (comment 14) [ 528.074530] usb 1-1.1: Manufacturer: JMicron [ 528.074531] usb 1-1.1: SerialNumber: 7D3200AA4B50 I am closing for the time being then. thanks to the anonymous fixer :-) cheers
Status: NEW => RESOLVEDResolution: (none) => FIXED
FI, This bug is back again with 4.1.15-desktop, seems that some kernel guys like to reintroduce some piece of code on a regular basis :-/ Same drive as before, worked fine since 4.1.8. cheers. [11212.089100] scsi host19: usb-storage 3-1.3:1.0 [11213.141532] scsi 19:0:0:0: Direct-Access Maxtor OneTouch II 023d PQ: 0 ANSI: 4 [11213.195027] sd 19:0:0:0: [sdj] 586114704 512-byte logical blocks: (300 GB/279 GiB) [11213.248761] sd 19:0:0:0: [sdj] Write Protect is off [11213.248767] sd 19:0:0:0: [sdj] Mode Sense: 24 00 00 00 [11213.302421] sd 19:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [11213.525689] sdj: sdj1 [11213.741295] sd 19:0:0:0: [sdj] Attached SCSI disk [11219.239971] XFS (dm-2): Mounting V4 Filesystem [11219.530792] XFS (dm-2): Starting recovery (logdev: internal) [11222.120611] XFS (dm-2): Ending recovery (logdev: internal) [11264.594697] blk_update_request: critical target error, dev sdj, sector 0 [11264.597196] blk_update_request: critical target error, dev sdj, sector 0 [11264.614685] blk_update_request: critical target error, dev sdj, sector 293301269 [11264.614709] XFS (dm-2): metadata I/O error: block 0x117b5415 ("xlog_iodone") error 121 numblks 64 [11264.614714] XFS (dm-2): xfs_do_force_shutdown(0x2) called from line 1180 of file fs/xfs/xfs_log.c. Return address = 0xffffffffc076bb56 [11264.614803] XFS (dm-2): Log I/O Error Detected. Shutting down filesystem [11264.614805] XFS (dm-2): Please umount the filesystem and rectify the problem(s) [11264.648885] XFS (dm-2): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5. [11264.649415] blk_update_request: critical target error, dev sdj, sector 293301333 [11264.649431] XFS (dm-2): metadata I/O error: block 0x117b5455 ("xlog_iodone") error 121 numblks 64 [11264.649435] XFS (dm-2): xfs_do_force_shutdown(0x2) called from line 1180 of file fs/xfs/xfs_log.c. Return address = 0xffffffffc076bb56 [11282.077492] XFS (dm-2): xfs_log_force: error -5 returned. [11312.056342] XFS (dm-2): xfs_log_force: error -5 returned.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Version: Cauldron => 5
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
In reply to: Chris Denice 2016-05-14 23:18:48 CEST Version: Cauldron => 5 Hi Chris :-) Thank you for having taken the needed time to report this issue! We regret if this issue didn't get fixed in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed. Closing as OLD.
CC: (none) => marja11Resolution: (none) => OLDStatus: REOPENED => RESOLVED