Description of problem: system treats free space for iriver ihp120 wrongly .., df yields /dev/sdb1 19507904 19179512 328392 99% /media/IHP-100 where there is at least 3GB free (windows displays it correctly) and it won't permitt to store more data that it thinks is free :( dmesg output related to that device ... usb 1-7: new high speed USB device using ehci_hcd and address 13 scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 13 usb-storage: waiting for device to settle before scanning Vendor: TOSHIBA Model: MK2004GAL Rev: JC10 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdb: 39063024 512-byte hdwr sectors (20000 MB) sdb: assuming drive cache: write through SCSI device sdb: 39063024 512-byte hdwr sectors (20000 MB) sdb: assuming drive cache: write through sdb: sdb1 Attached scsi disk sdb at scsi5, channel 0, id 0, lun 0 usb-storage: device scan complete FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! usb 1-7: USB disconnect, address 13 Version-Release number of selected component (if applicable): kernel 2.6.10-1.766_FC3 How reproducible: always Steps to Reproduce: 1. plug the device in 2. execute df command 3. try to save more than df says it is free Actual results: system limits usage of the device in the way of determination of free space wrongly Expected results: system should determine free space correctly Additional info:
I also have this problem, but with an external usb hard drive. I have a seagate 160GB usb hard drive with ~90GB of data on it, but df reports only 12GB used (148GB free). From dmesg: usb-storage: device scan complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: assuming drive cache: write through SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: assuming drive cache: write through sda: sda1 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
it works fine now, thanks :)
scalapack-2.0.2-5.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/scalapack-2.0.2-5.el7