Closed GoogleCodeExporter closed 9 years ago
I forgot to specify : RT-N16 issue !!!!
Original comment by jbcantou...@gmail.com
on 14 Nov 2010 at 11:40
Another related issue : sometimes, on restart, the disk is not visible on samba
network (not mounted ?)
Original comment by jbcantou...@gmail.com
on 15 Nov 2010 at 12:04
Here should be an help :
http://ubuntuforums.org/showthread.php?t=1312553
Original comment by jbcantou...@gmail.com
on 15 Nov 2010 at 12:23
And a last one for you coders :
http://www.google.fr/search?sourceid=chrome&ie=UTF-8&q=random+files+missing+samb
a
thanks !
Original comment by jbcantou...@gmail.com
on 15 Nov 2010 at 12:32
First of all, we are non-profit community and haven't any "coders".
Second, you even don't tell us which build exactly you tested.
Third, I can't reproduce bug, probably because I haven't Windows at all.
Do workaround suggested helps you?
"Just as an additional data point: could you try mounting with the
"noserverino" option, and let us know if that fixes the problem?"
I agree that cifs subsystem, as many others, needs more fixes from upstream,
but we simply can't maintain linux kernel as good as it done by Linus.
Related upstream commits
a364bc0b37f14ffd66c1f982af42990a9d77fa43
ddb4cbfc53aa0913ee8da059fcbf628d14f40f63
f12f98dba6ea1517cd7fbb912208893b9c014c15
db19272edc93661835bf6ec9736cfd0754aa3c62
4065c802da7484fa36f8cdf10f18d087233ecb88
is it that solution what you mean?
Original comment by lly.dev
on 16 Nov 2010 at 7:08
[deleted comment]
I had such issues with filenames in unicode, the workaround was renaming.
Original comment by vladimir...@gmail.com
on 31 May 2011 at 6:04
Could you provide some examples of such filenames?
Original comment by lly.dev
on 27 Jun 2012 at 7:15
Regarding the wrong/unexpected filenames, as it is NTFS formatted (item 3 of
#c0), I'm guessing this has to do with codepage settings. Have you modified
"smb.conf" or are you using the default configuration in the firmware? Are the
"missing" files the ones that use non-ASCII (non-English) characters?
Also, regarding the "real size" and "size on disk" (item 3 of #c0), are you
using NTFS compression on the whole drive or parts of it (the "Compress this
drive to save disk space" setting)? That might explain the "wrong" heuristics...
I believe it would be valuable if you run "chkdsk" from a command prompt on
your Windows machine and copy+paste/attach the result here.
Original comment by helder.magalhaes
on 18 Aug 2012 at 7:33
NTFS filesystem access provided by ntfs3g driver + FUSE subsystem. Unless we
will has reproducible test-case, we can't neither open issue on ntfs3g project,
nor try to backport fixes/improvements of FUSE subsystem.
Original comment by lly.dev
on 4 Oct 2012 at 6:22
Original issue reported on code.google.com by
jbcantou...@gmail.com
on 14 Nov 2010 at 11:38