Bug#777644: linux: UDF complains about inode size of file it just created

2015-02-10 Thread brian m. carlson

Package: src:linux
Version: 3.18.3-1~exp1
Severity: normal

I have a 16 GB USB flash drive formatted with UDF.  I copied a file to 
it and ejected it, then inserting it into a Windows machine, which 
complained it was corrupt.  Removing the file and copying it again 
resulted in the same effect.


As you can see from the kernel log below, UDF-fs (udf_evict_inode) is 
complaining about the file it just created.  If the way it created the 
file is defective (and both it and Windows seem to think so), it should 
avoid creating the file in such a way and instead create it in a 
non-defective way.  It should definitely create the file in a way that 
is likely to work across a wide variety of systems, as that's the reason 
I formatted it UDF.


The UDF file system was created on this system (amd64/sid) a couple 
months ago.  I tried copying the file using cp and caja.  I tried 
ejecting the disk both using caja and a manual umount.


-- Package-specific info:
** Version:
Linux version 3.18.0-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-9) ) #1 SMP Debian 3.18.3-1~exp1 (2015-01-18)

** Command line:
BOOT_IMAGE=/vmlinuz-3.18.0-trunk-amd64 root=/dev/mapper/vauxhall-root ro 
i8042.reset=1 i8042.nomux=1 audit=0 i8042.reset=1 i8042.nomux=1 audit=0

** Not tainted

** Kernel log:
[292312.257032] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[292312.439719] UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2014/11/10 
00:53 (1000)
[292375.751893] UDF-fs: warning (device sdb1): udf_evict_inode: Inode 1908771 
(mode 100644) has inode size 587416 different from extent length 588800. 
Filesystem need not be standards compliant.
[292394.563950] usb 2-1.2: USB disconnect, device number 9
[292397.322674] usb 2-1.2: new high-speed USB device number 10 using ehci-pci
[292397.416887] usb 2-1.2: New USB device found, idVendor=0930, idProduct=6545
[292397.416897] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[292397.416901] usb 2-1.2: Product: TransMemory-Mx
[292397.416905] usb 2-1.2: Manufacturer: TOSHIBA
[292397.416910] usb 2-1.2: SerialNumber: EDB060003E83
[292397.417482] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[292397.417682] scsi host8: usb-storage 2-1.2:1.0
[292398.415989] scsi 8:0:0:0: Direct-Access TOSHIBA  TransMemory-Mx   PMAP 
PQ: 0 ANSI: 6
[292398.416894] sd 8:0:0:0: Attached scsi generic sg2 type 0
[292398.417332] sd 8:0:0:0: [sdb] 30464640 512-byte logical blocks: (15.5 
GB/14.5 GiB)
[292398.418163] sd 8:0:0:0: [sdb] Write Protect is off
[292398.418172] sd 8:0:0:0: [sdb] Mode Sense: 45 00 00 00
[292398.419030] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[292399.750543]  sdb: sdb1
[292399.754389] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[292399.966395] UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2014/11/10 
00:53 (1000)
[292404.687415] atkbd serio0: Unknown key pressed (raw set 2, code 0x0 on 
isa0060/serio0).
[292404.687427] atkbd serio0: Use 'setkeycodes 00 keycode' to make it known.
[292433.399913] atkbd serio0: Unknown key pressed (raw set 2, code 0x0 on 
isa0060/serio0).
[292433.399925] atkbd serio0: Use 'setkeycodes 00 keycode' to make it known.
[292440.555262] UDF-fs: warning (device sdb1): udf_evict_inode: Inode 1908771 
(mode 100600) has inode size 587416 different from extent length 588800. 
Filesystem need not be standards compliant.
[292453.203130] usb 2-1.2: USB disconnect, device number 10
[292455.706475] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
[292455.800401] usb 2-1.2: New USB device found, idVendor=0930, idProduct=6545
[292455.800419] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[292455.800422] usb 2-1.2: Product: TransMemory-Mx
[292455.800425] usb 2-1.2: Manufacturer: TOSHIBA
[292455.800428] usb 2-1.2: SerialNumber: EDB060003E83
[292455.800877] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[292455.801361] scsi host9: usb-storage 2-1.2:1.0
[292456.800075] scsi 9:0:0:0: Direct-Access TOSHIBA  TransMemory-Mx   PMAP 
PQ: 0 ANSI: 6
[292456.801044] sd 9:0:0:0: Attached scsi generic sg2 type 0
[292456.801606] sd 9:0:0:0: [sdb] 30464640 512-byte logical blocks: (15.5 
GB/14.5 GiB)
[292456.803504] sd 9:0:0:0: [sdb] Write Protect is off
[292456.803516] sd 9:0:0:0: [sdb] Mode Sense: 45 00 00 00
[292456.806942] sd 9:0:0:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[292458.137284]  sdb: sdb1
[292458.140804] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[292458.351181] UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2014/11/10 
00:53 (1000)
[292489.820820] usb 2-1.2: USB disconnect, device number 11
[292492.068117] usb 2-1.2: new high-speed USB device number 12 using ehci-pci
[292492.162666] usb 2-1.2: New USB device found, idVendor=0930, idProduct=6545
[292492.162675] usb 2-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[292492.162680] usb 

Bug#777644: linux: UDF complains about inode size of file it just created

2015-02-10 Thread Ben Hutchings
Control: tag -1 moreinfo

On Wed, 2015-02-11 at 01:58 +, brian m. carlson wrote:
 Package: src:linux
 Version: 3.18.3-1~exp1
 Severity: normal
 
 I have a 16 GB USB flash drive formatted with UDF.  I copied a file to 
 it and ejected it, then inserting it into a Windows machine, which 
 complained it was corrupt.  Removing the file and copying it again 
 resulted in the same effect.
 
 As you can see from the kernel log below, UDF-fs (udf_evict_inode) is 
 complaining about the file it just created.  If the way it created the 
 file is defective (and both it and Windows seem to think so), it should 
 avoid creating the file in such a way and instead create it in a 
 non-defective way.  It should definitely create the file in a way that 
 is likely to work across a wide variety of systems, as that's the reason 
 I formatted it UDF.
 
 The UDF file system was created on this system (amd64/sid) a couple 
 months ago.  I tried copying the file using cp and caja.  I tried 
 ejecting the disk both using caja and a manual umount.
[...]

There was a fix in 3.18.6 that looks like it might be related to this;
please try that.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


signature.asc
Description: This is a digitally signed message part


Processed: Re: Bug#777644: linux: UDF complains about inode size of file it just created

2015-02-10 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #777644 [src:linux] linux: UDF complains about inode size of file it just 
created
Added tag(s) moreinfo.

-- 
777644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b777644.142363047712719.transcr...@bugs.debian.org