Bug with long file names

Bugs and issues
#1

Capture

I’m getting a bunch of sync errors on my files. I suspect it’s because the file name is very long. On the other hand, Google’s Backup and Sync can handle it. It could also be because I have 2 files with very long file names that only differ at the very very end, probably after it has gone beyond Window’s file length limit. However, Google’s backup and sync handles it. The 2 file names are:

Your invoice for eBay purchases- 20MM WHITE Nylon NATO Military WATCH BAND Strap G-10 (200707955108#),22MM NATO Style MILITARY WATCH BAND SOLID Strap G-10 FITS TIMEX NEW!! (200653227270#),22MM JAMES BOND NATO Style MILITARY WATCH BAND STRIPPED S.eml

and…

Your invoice for eBay purchases- 20MM WHITE Nylon NATO Military WATCH BAND Strap G-10 (200707955108#),22MM NATO Style MILITARY WATCH BAND SOLID Strap G-10 FITS TIMEX NEW!! (200653227270#),22MM JAMES BOND NATO Style MILITARY WATCH BAND STRIPPED S-1.eml

And the way Google drive syncs these 2 files is with the names:

Your invoice for eBay purchases- 20MM WHITE Nylon NATO Military WATCH BAND Strap G-10 (200707955108#),22MM NATO Style MILITARY WATCH BAND SOLID Strap G-10 FITS TIMEX NEW!! (200653227270#),22.eml

and…

Your invoice for eBay purchases- 20MM WHITE Nylon NATO Military WATCH BAND Strap G-10 (200707955108#),22MM NATO Style MILITARY WATCH BAND SOLID Strap G-10 FITS TIMEX NEW!! (200653227270#),22 (1).eml

So apparently Google backup and sync has an algorithm for shortening super long file names. However insynch seems to just fail in this case.

This is a bug, right?

#2

Hi there,

Yes it is. We have one or two reports on this. Can you send us your logs.db and out.txt along with the link to this post to support@insynchq.com?

New Insync version: 3.0.28
#3

I see this bug still exists in 3.1.0. I’m kinda tired after 4 months of seeing the litle “insync fail” (!) icon on my status bar. Any chance this will be fixed any time soon?

#4

Hi! May I confirm if it’s the same Invalid argument error you’re seeing on 3.1.0.40756, @xpusostomos?

#5

The error is exactly the same as in the original screen shot, namely “unexpected error doing addlocalgditem [errno22] invalid argument.”

1 Like
#6

Hi @xpusostomos,

I see. Can you confirm if you’re on v3.1.0.40756, and not 3.1.0.40752?

#7

I’m on v3.1.0.40756

…

#8

This error is currently lined up in their timeline but will confirm when it will be fixed. Thank you for following up!

#9

It is almost September 2024 and I’m still faced with bunches of “filename too long” errors! in Insync version 3.9.4.60020

#10

Hello! My apologies for the trouble. Filename too long errors can be caused by a few things. Please send your logs.db and out.txt files to support@insynchq.com with the link to this post. They should be in ~/.config/Insync, or you can follow this guide.

Thank you!

#11

what few things? That’s the sort of list that should be documented and supplied anyone someone asks about it.

#12

@xpusostomos The most common is that the file name is actually too long for the filesystem to accept it. I’ll be discussing this error with our engineers so we can document accordingly in our Help Center. Thanks for the feedback. :slight_smile: