fuse-exfat-1.1.0, ERROR: file system is larger than underlying device

[seb]

Hi,

I have a Panasonic Lumix DMC TZ-40 camera with a 64 GB SD card. The exFAT filesystem of the SD card has been created by the camera at the first usage.
After upgrading 2 of my 4 computers from Debian Wheezy 7.0 (fuse exfat 0.9.2) to Debian Jessie 8.0 (fuse exfat 1.1.0), I discovered that my camera does not work anymore with fuse-exfat 1.1.0.


So I have tried to compile older versions of fuse-exfat to discover when the regression appears.


When I plug the camera on a USB port of my computer, and try to mount the exfat partition

as read-only.

It works at least with fuse-exfat version 0.9.2, 1.0.0, 1.0.1
# mount.exfat /dev/sdb1 /mnt

FUSE exfat 1.0.1
WARN: `/dev/sdb1' is write-protected, mounting read-only.

I can get the pictures in /mnt


But it fails with fuse-exfat-1.1.0 it says
# mount.exfat /dev/sdb1 /mnt
FUSE exfat 1.1.0
WARN: '/dev/sdb1' is write-protected, mounting read-only.
ERROR: file system is larger than underlying device: 63467159552 > 63467159040.

and I have nothing in /mnt

I have also tried with the last SVN version (today 2015-01-17), and I get the same error message: ERROR: file system is larger than underlying device: 63467159552 > 63467159040.


Conclusion:
- for me the solution is to switch back to fuse-exfat-1.0.1- for read-only filesystem, mount.exfat may print some warning message instead of aborting on error.


for information

# uname -a
Linux mycomputer 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) i686 GNU/Linux
# dmesg
[ 1403.820069] usb 1-7: new high-speed USB device number 3 using ehci-pci
[ 1403.953778] usb 1-7: New USB device found, idVendor=04da, idProduct=2372
[ 1403.953784] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1403.953788] usb 1-7: Product: DMC-TZ40
[ 1403.953791] usb 1-7: Manufacturer: Panasonic
[ 1403.953794] usb 1-7: SerialNumber: 0000000000000000000F1104010681
[ 1404.054371] usb-storage 1-7:1.0: USB Mass Storage device detected
[ 1404.055048] usb-storage 1-7:1.0: Quirks match for vid 04da pid 2372: 90
[ 1404.055092] scsi2 : usb-storage 1-7:1.0
[ 1404.055256] usbcore: registered new interface driver usb-storage
[ 1405.053029] scsi 2:0:0:0: Direct-Access MATSHITA DMC-TZ40 0120 PQ: 0 ANSI: 5
[ 1405.053733] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 1405.071619] sd 2:0:0:0: [sdb] Adjusting the sector count from its reported value: 123992064
[ 1405.071632] sd 2:0:0:0: [sdb] 123992063 512-byte logical blocks: (63.4 GB/59.1 GiB)
[ 1405.091263] sd 2:0:0:0: [sdb] Write Protect is on
[ 1405.091271] sd 2:0:0:0: [sdb] Mode Sense: 23 00 80 00
[ 1405.110998] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[ 1405.112636] sd 2:0:0:0: [sdb] Adjusting the sector count from its reported value: 123992064
[ 1405.282012] sdb: sdb1
[ 1405.282021] sdb: p1 size 123959296 extends beyond EOD, enabling native capacity
[ 1405.282731] sd 2:0:0:0: [sdb] Adjusting the sector count from its reported value: 123992064
[ 1405.342634] sdb: sdb1
[ 1405.342642] sdb: p1 size 123959296 extends beyond EOD, truncated
[ 1405.343985] sd 2:0:0:0: [sdb] Adjusting the sector count from its reported value: 123992064
[ 1405.380990] sd 2:0:0:0: [sdb] Attached SCSI removable disk



best regards
---
koopa

[Andrew Nayenko]

Hi,

> After upgrading 2 of my 4 computers from Debian Wheezy 7.0 (fuse exfat 0.9.2) to Debian Jessie 8.0 (fuse exfat 1.1.0), I discovered that my camera does not work anymore with fuse-exfat 1.1.0.
>
> So I have tried to compile older versions of fuse-exfat to discover when the regression appears.
>
> When I plug the camera on a USB port of my computer, and try to mount the exfat partition
>
> as read-only.
>
> It works at least with fuse-exfat version 0.9.2, 1.0.0, 1.0.1
>

> But it fails with fuse-exfat-1.1.0 it says
> # mount.exfat /dev/sdb1 /mnt
> FUSE exfat 1.1.0
> WARN: '/dev/sdb1' is write-protected, mounting read-only.
> ERROR: file system is larger than underlying device: 63467159552 > 63467159040.

This means that fuse-exfat cannot access the whole volume. This may be
a bug in FS creation utility or Linux kernel, but fuse-exfat can do
nothing with this.

> Conclusion:
> - for me the solution is to switch back to fuse-exfat-1.0.1

This is a bad idea. You will not be able to read a file if one of its
clusters is placed at the end of the volume. Besides, fuse-exfat 1.0.1
contains known bugs, so you can get other problems.

The proper solution is to recreate the FS using mkfs.exfat utility on your PC.

--
Andrew Nayenko <res...@gmail.com>

[mark.regi...@gmail.com]

On Tuesday, January 20, 2015 at 8:43:55 PM UTC+11, Andrew Nayenko wrote:

The proper solution is to recreate the FS using mkfs.exfat utility on your PC.

I'm getting the same problem being unable to mount a Lumix camera after an OS upgrade:

"ERROR: file system is larger than underlying device: 64037584896 > 64037584384"

Reformatting the card from the camera doesn't fix the problem, so I'm not sure that a re-format from Linux is a good idea.

[Andrew Nayenko]

>> The proper solution is to recreate the FS using mkfs.exfat utility on your
>> PC.
>
> I'm getting the same problem being unable to mount a Lumix camera after an
> OS upgrade:
> "ERROR: file system is larger than underlying device: 64037584896 >
> 64037584384"
>
> Reformatting the card from the camera doesn't fix the problem, so I'm not
> sure that a re-format from Linux is a good idea.

Unfortunately, I have no other solution for this situation.

--
Andrew Nayenko <res...@gmail.com>

[fra...@thibault.org]

I ran into this problem with my Lumix camera (GX7), but I can read and write the same card with a Transcend SDXC card reader:

http://www.amazon.com/gp/product/B009D79VH4

So I guess it's a bug in the Panasonic firmware, not in fuse-exfat.

[seb]

Thank for the information, it is very interesting. Yes I think also that it is a bug in the Panasonic firmware.

Nevertheless mount.exfat may be less picky for read-only filesystem, it may print some warning message instead of aborting on error.

---

De : "fra...@thibault.org" <fra...@thibault.org>
À : ex...@googlegroups.com
Cc : koop...@yahoo.fr
Envoyé le : Jeudi 23 avril 2015 2h20
Objet : Re: fuse-exfat-1.1.0, ERROR: file system is larger than underlying device

I ran into this problem with my Lumix camera (GX7), but I can read and write the same card with a Transcend SDXC card reader:

http://www.amazon.com/gp/product/B009D79VH4

So I guess it's a bug in the Panasonic firmware, not in fuse-exfat.

On Saturday, January 17, 2015 at 9:59:16 AM UTC-5, seb wrote:

Hi,

I have a Panasonic Lumix DMC TZ-40 camera with a 64 GB SD card. The exFAT filesystem of the SD card has been created by the camera at the first usage.
After upgrading 2 of my 4 computers from Debian Wheezy 7.0 (fuse exfat 0.9.2) to Debian Jessie 8.0 (fuse exfat 1.1.0), I discovered that my camera does not work anymore with fuse-exfat 1.1.0.

So I have tried to compile older versions of fuse-exfat to discover when the regression appears.

When I plug the camera on a USB port of my computer, and try to mount the exfat partition as read-only.

It works at least with fuse-exfat version 0.9.2, 1.0.0, 1.0.1
# mount.exfat /dev/sdb1 /mnt

FUSE exfat 1.0.1
WARN: `/dev/sdb1' is write-protected, mounting read-only.

I can get the pictures in /mnt

But it fails with fuse-exfat-1.1.0 it says
# mount.exfat /dev/sdb1 /mnt
FUSE exfat 1.1.0
WARN: '/dev/sdb1' is write-protected, mounting read-only.
ERROR: file system is larger than underlying device: 63467159552 > 63467159040.

and I have nothing in /mnt

I have also tried with the last SVN version (today 2015-01-17), and I get the same error message: ERROR: file system is larger than underlying device: 63467159552 > 63467159040.

Conclusion:
- for me the solution is to switch back to fuse-exfat-1.0.1- for read-only filesystem, mount.exfat may print some warning message instead of aborting on error.

best regards
---
koopa

[christop...@gmail.com]

Might be slightly off-sides, but I had this same issue for likely a completely unrelated reason. I ported fuse-exfat-1.1.0 to a non-Linux OS. The issue was, for me, that my implementation of lseek was returning a 32-bit integer instead of a 64-bit off_t. So even though I formatted my 8GB memory stick as ExFAT in Windows just fine, my other OS thought the volume was bigger than the drive.

[barl...@gmail.com]

I am seeing the same problem with my Panasonic FZ200 (64GB SD card), although the 64.... numbers are slightly different.  Unfortunately I can't just use the card reader on my computer - it did not work with either that card or the 8GB card from a Canon camera.  I can load both cards with the card reader on my laptop though, which uses an older exfat-fuse. 

I can (sort of) get pictures off the camera using PictBridge mode, but that does not work for videos and some of the stills are read-only.  I would really like to mount the card read-write to get those videos off.

gthumb works beautifully with the Canon camera, so I admit Panasonic has a bug, but couldn't exfat-fuse be more forgiving?  It used to work fine with my Panasonic...and even though Panasonic must be doing something wrong, the error message users get from exfat-fuse when they update from 1.0.1 to 1.1.0 gives the impression that the card had suffered a filesystem error, when the change was really in exfat-fuse.  Has anyone tried running fsck or mkfs.exfat?  I'm very reluctant to go that route - if it makes the card incompatible with the camera then there's not much I can do on the camera to make it compatible with Linux (and then I'd have reformat the card through the camera, which would bring us back to where we started).

Thanks,

Rob

[barl...@gmail.com]

I fetched the source of fuse-exfat-1.1.0 (see https://code.google.com/p/exfat/wiki/HOWTO ) and changed line 257 of libexfat/mount.c to

 if (0 && (le64_to_cpu(ef->sb->sector_count) * SECTOR_SIZE(*ef->sb) >
          exfat_get_size(ef->dev)))

i.e. I disabled the check that was failing.  IMHO it would be better to refine the test to if !Panasonic and/or the difference is greater than some number (from what I've seen, the Panasonic discrepancy is very small), but since it now connects to my camera I quit while I was ahead.

[Andrew Nayenko]

Hi Rob,

> couldn't exfat-fuse be more forgiving? It used to work fine with
> my Panasonic...and even though Panasonic must be doing something wrong, the
> error message users get from exfat-fuse when they update from 1.0.1 to 1.1.0
> gives the impression that the card had suffered a filesystem error, when the
> change was really in exfat-fuse.

I quite agree that this is a bad user experience. Of course fuse-exfat
can issue a warning on mount and allow full access to the filesystem,
but who will notice this warning? Most people use graphical
environments. They will find out that something went wrong only when
I/O fails.

From the other hand access the unreachable cluster will happen rarely.
There are much more people who face the error on mount.

OK, I'll turn this error into warning. Looks like this will improve
overall user experience.

--
Andrew Nayenko <res...@gmail.com>

[Rob Reid]

Thank you.  I agree that it is a thorny problem and users typically ignore or don't see warnings when they use a wrapper.  The code I posted was only intended for people like me with Panasonic cameras and had ended up reading this thread.