Bug#763966: linux-image-3.16-2-amd64: Fail to write on ext3 filesystem of an external USB hard drive
On Sun, Nov 09, 2014 at 01:22:31PM +0100, Bastian Blank wrote: On Sat, Oct 04, 2014 at 12:53:29PM +0200, Sebastien Helleu wrote: ** Tainted: I (2048) * Working around severe firmware bug. You may want to search for a fixed firmware, but this may be irrelevant for the current problem. ** Kernel log: [...] This log does not show any message similar to the ones shown before. Please provide complete logs. Bastian -- We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu! Hi Bastian, Here are the errors I have with kernel 3.17-1 (Linux omega 3.17-1-amd64 #1 SMP Debian 3.17-1~exp1 (2014-10-14) x86_64 GNU/Linux): Nov 22 09:18:02 omega kernel: [ 1120.392369] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem Nov 22 09:18:02 omega kernel: [ 1120.411984] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) Nov 22 09:18:10 omega kernel: [ 1128.721413] end_request: critical target error, dev sdc, sector 12447 Nov 22 09:18:10 omega kernel: [ 1128.721433] Aborting journal on device sdc1-8. Nov 22 09:18:32 omega kernel: [ 1150.220476] EXT4-fs error (device sdc1): ext4_journal_check_start:56: Detected aborted journal Nov 22 09:18:32 omega kernel: [ 1150.220495] EXT4-fs (sdc1): Remounting filesystem read-only I found that other people have similar problem with recent kernels, for example: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366538 This external USB drives works perfectly fine with any kernel = 3.14 (when booting this kernel on the same machine, so exactly same hardware/softare installed). And with a kernel 3.14, I'm not able at all to write on the disk. That's why I'm almost sure the problem is in Linux kernel. Cordialement / Best regards. -- Sébastien Helleu web: flashtux.org / weechat.org mail: flashc...@flashtux.org irc: FlashCode @ irc.freenode.netxmpp: flashc...@jabber.fr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763966: linux-image-3.16-2-amd64: Fail to write on ext3 filesystem of an external USB hard drive
I found my drive (Maxtor OneTouch II) is reporting a write cache, which makes the kernel issue SYNCHRONIZE_CACHE requests, but the drive does not support SYNCHRONIZE_CACHE. A change in the 3.16 SCSI layer makes flush errors get processed correctly instead of ignored. I just reported the issue to linux-scsi to start. I'm thinking this will end up as a USB storage quirk. -- Jeff DeFouw m...@plorb.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763966: linux-image-3.16-2-amd64: Fail to write on ext3 filesystem of an external USB hard drive
On Sat, Oct 04, 2014 at 12:53:29PM +0200, Sebastien Helleu wrote: ** Tainted: I (2048) * Working around severe firmware bug. You may want to search for a fixed firmware, but this may be irrelevant for the current problem. ** Kernel log: [...] This log does not show any message similar to the ones shown before. Please provide complete logs. Bastian -- We'll pivot at warp 2 and bring all tubes to bear, Mr. Sulu! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763966: linux-image-3.16-2-amd64: Fail to write on ext3 filesystem of an external USB hard drive
Package: src:linux Version: 3.16.3-2 Severity: important Dear Maintainer, I'm not able to write on my USB external hard drive, which has filesystem ext3. Here are the steps and error messages I got: root@omega:~# mount -t ext3 /dev/sdc1 /mnt/lacie No error, mount is OK: root@omega:~# mount (...) /dev/sdc1 on /mnt/lacie type ext3 (rw,relatime,data=ordered) In /var/log/syslog: Oct 4 12:04:12 omega kernel: [ 121.633614] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem Oct 4 12:04:12 omega kernel: [ 121.654928] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) I can read the files on the disk. When I try to create a new empty file in the root of disk: root@omega:/mnt/lacie# touch test touch: cannot touch ‘test’: Read-only file system I have this error in /var/log/syslog: Oct 4 12:08:19 omega kernel: [ 368.481482] EXT4-fs error (device sdc1): ext4_journal_check_start:56: Detected aborted journal Oct 4 12:08:19 omega kernel: [ 368.481494] EXT4-fs (sdc1): Remounting filesystem read-only Sometimes I have this error: Oct 4 11:28:54 omega kernel: [11711.588781] EXT4-fs error (device sdc1): ext4_put_super:792: Couldn't clean up the journal Oct 4 11:28:58 omega kernel: [11715.746328] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem After these errors, the filesystem is automatically remonted as read-only. Therefore I'm not able at all to write on the disk. Just for info, the output of e2fsck (nothing relevant for me): root@omega:~# umount /mnt/lacie/ root@omega:~# e2fsck /dev/sdc1 e2fsck 1.42.12 (29-Aug-2014) /dev/sdc1: recovering journal /dev/sdc1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sdc1: 444283/39075840 files (6.7% non-contiguous), 45617307/78142160 blocks The output of dumpe2fs: root@omega:~# dumpe2fs -h /dev/sdc1 dumpe2fs 1.42.12 (29-Aug-2014) Filesystem volume name: none Last mounted on: /mnt/lacie Filesystem UUID: e739879e-05a9-4588-92c1-8c5811f510a3 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file Filesystem flags: signed_directory_hash Default mount options:(none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 39075840 Block count: 78142160 Reserved block count: 3907108 Free blocks: 32524853 Free inodes: 38631557 First block: 0 Block size: 4096 Fragment size:4096 Reserved GDT blocks: 1005 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16384 Inode blocks per group: 512 Filesystem created: Thu Apr 12 22:20:33 2007 Last mount time: Sat Oct 4 12:26:00 2014 Last write time: Sat Oct 4 12:26:56 2014 Mount count: 0 Maximum mount count: -1 Last checked: Sat Oct 4 12:26:56 2014 Check interval: 15552000 (6 months) Next check after: Thu Apr 2 12:26:56 2015 Lifetime writes: 291 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode:8 Default directory hash: tea Directory Hash Seed: 2c8ade12-c8ec-4c9a-ab81-a6471f9bcb62 Journal backup: inode blocks Journal features: journal_incompat_revoke Journal size: 128M Journal length: 32768 Journal sequence: 0x00029ca0 Journal start:0 I have same problem with kernel in package linux-image-3.17-rc5-amd64. Kernels in linux-image-3.14-2-amd64 or older works fine. -- Package-specific info: ** Version: Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64 root=UUID=28fbcb8c-10a9-49d8-a825-29842c8a1365 ro initrd=/install/initrd.gz quiet ** Tainted: I (2048) * Working around severe firmware bug. ** Kernel log: [1.605631] Bluetooth: hci0: read Intel version: 370710018002030d37 [1.605634] Bluetooth: hci0: Intel device is already patched. patch num: 37 [1.605996] [drm] VBT doesn't support DRRS [1.607260] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [1.608573] iwlwifi :02:00.0: Detected Intel(R) Wireless N 7260, REV=0x144 [1.608620] iwlwifi :02:00.0: L1 Disabled; Enabling L0S [1.608839] iwlwifi :02:00.0: L1 Disabled; Enabling L0S [1.610035] alg: No test for crc32 (crc32-pclmul) [1.612865] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro [
