Public bug reported:

Binary package hint: devicekit-disks

After upgrading to Karmic, the script I was using to back up my data (to
an NTFS formatted external hard drive) no longer works (my ext3
formatted external hard drive still works fine).

The disk mounts with the following options when I plug it in (from mount -l):
/dev/sdb1 on /media/MEDIABOX type vfat 
(rw,nosuid,nodev,uhelper=devkit,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,flush)
 [MEDIABOX]

I thought it mounted as ntfs previously, but my recollection on that
point may be wrong.  I can't get it to mount as ntfs now.

The following problems result when I run the rsync command that worked
previously:

1. rsync tries to copy far more files than it should (possibly too many
even if --size-only is set; if --size-only is not set, it tries to copy
basically everything, even though I am using --modify-window=1)

2. rsync yields the following errors, even if run with sudo:
rsync: mkstemp "[filename on external HD]" failed: Read-only file system (30)
rsync: failed to set times on "[filename on external HD]": Read-only file 
system (30)
[... many, many instances of those same errors ...]

3. Looking at syslog yields the following:
Nov  7 14:51:28 system42 kernel: [100893.332080] FAT: Filesystem error (dev 
sdb1)
Nov  7 14:51:28 system42 kernel: [100893.332103]     fat_free_clusters: 
deleting FAT entry beyond EOF
Nov  7 14:51:28 system42 kernel: [100893.332112]     File system has been set 
read-only

That looks troublingly like a bug described here:
http://www.osnews.com/story/9681/The_vfat_file_system_and_Linux/page3/

Troubling because that article claims:
Under Linux Kernel 2.4.x., a limit of the cluster data type results in data 
loss, as soon as the vfat file system holds around 130GB. In Kernel 2.6.x., 
this problem was - rather accidently - solved...

(The drive I'm using is 500GB and mostly full, 435 GB used.)

And I am indeed running a 2.6 kernel:
$ uname -r
2.6.31-14-generic

So is this a regression of a kernel bug?

The data on the disk hasn't been lost or corrupted as far as I can tell,
though I don't really feel I can trust the backup files touched by rsync
post upgrade (at least not until I can rerun it after this problem is
fixed).

Looking at the disk in nautilis confirms that it has indeed been set
read-only.  If I unmount and remove the disk, then plug it in again, it
remounts, and I can again read and write files.  Running rsync again
still results in the same problem.

Submitting this to devicekit-disks because I guess it has something to
do with the disk mounting differently in Karmic than it did in
Intrepid... although the problem could well lie elsewhere.

ProblemType: Bug
Architecture: amd64
CustomUdevRuleFiles: 45-libgphoto2.rules~
Date: Sat Nov  7 14:53:16 2009
DistroRelease: Ubuntu 9.10
MachineType: System76, Inc. Pangolin Performance
NonfreeKernelModules: openafs nvidia
Package: devicekit-disks 007-2ubuntu3 [modified: usr/bin/devkit-disks 
usr/lib/devicekit-disks/devkit-disks-daemon 
usr/lib/devicekit-disks/devkit-disks-helper-mkfs 
usr/lib/devicekit-disks/devkit-disks-helper-delete-partition 
usr/lib/devicekit-disks/devkit-disks-helper-create-partition 
usr/lib/devicekit-disks/devkit-disks-helper-modify-partition 
usr/lib/devicekit-disks/devkit-disks-helper-create-partition-table 
usr/lib/devicekit-disks/devkit-disks-helper-change-filesystem-label 
usr/lib/devicekit-disks/devkit-disks-helper-linux-md-remove-component 
usr/lib/devicekit-disks/devkit-disks-helper-fstab-mounter 
usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect 
usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-selftest 
usr/lib/devicekit-disks/devkit-disks-helper-drive-detach 
usr/lib/devicekit-disks/devkit-disks-helper-drive-poll 
usr/lib/devicekit-disks/devkit-disks-helper-linux-md-check 
lib/udev/devkit-disks-part-id lib/udev/devkit-disks-dm-export 
lib/udev/devkit-disks-probe-ata-smart sbin/umount.devkit]
ProcCmdLine: root=UUID=e7728359-15b1-4eb6-a7c9-db1b40e7c807 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: devicekit-disks
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 04/06/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 1.02.22
dmi.board.asset.tag: Tag 12345
dmi.board.name: Pangolin Performance
dmi.board.vendor: System76, Inc.
dmi.board.version: panp5
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.02.22:bd04/06/2009:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp5:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp5:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Pangolin Performance
dmi.product.version: panp5
dmi.sys.vendor: System76, Inc.

** Affects: devicekit-disks (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug

-- 
vfat external hard drive goes read-only during rsync
https://bugs.launchpad.net/bugs/477773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to