Date: Thu, 1 May 2014 15:35:52 -0400 From: Henry Hu <henry.hu.sh@gmail.com> To: =?UTF-8?B?TWFya28gQ3VwYcSH?= <marko.cupac@mimar.rs> Cc: freebsd-stable@freebsd.org Subject: Re: file corruption possibly related to fuse Message-ID: <CAEJt7hbd5ORuAa3xnQYjC9GngihYuyuTc9W0AhaDfhr7bkm7zA@mail.gmail.com> In-Reply-To: <20140501211803.22e1bd676877c3538ba63ac6@mimar.rs> References: <20140501211803.22e1bd676877c3538ba63ac6@mimar.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 1, 2014 at 3:18 PM, Marko Cupa=C4=87 <marko.cupac@mimar.rs> wro=
te:
> I see this problem for the third time in a few months, so I thought I
> should share with someone.
>
> I am on 10.0-RELEASE-p1 amd64. Copying files to external FAT or NTFS
> formatted USB disks ends up with bunch of strangely named files which
> can't be deleted, similar to:
>
> pacija@kaa:~/mnt/somefolder % ls -ilh
> ls: &=EF=BF=BD=EF=BF=BD?(?=EF=BF=BD?.=EF=BF=BDL?: Invalid argument
> ls: '?=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDo=EF=BF=BD.=EF=BF=BD?=EF=BF=BD:=
Invalid argument
> ls: +?-??x_~.s=EF=BF=BD : Invalid argument
> ls: /=EF=BF=BD~?=EF=BF=BD=EF=BF=BD=EF=BF=BD?.?i=EF=BF=BD: No such file or=
directory
> ls: :o&Rv1=EF=BF=BD=EF=BF=BD.=EF=BF=BD?f: Invalid argument
> ls: :=EF=BF=BD???f?z.w=EF=BF=BD=EF=BF=BD: Invalid argument
> ls: ;m=EF=BF=BD?2?=EF=BF=BDy.=EF=BF=BD=EF=BF=BD}: Invalid argument
> ls: <?=EF=BF=BDo=EF=BF=BDs^=EF=BF=BD.=EF=BF=BD=EF=BF=BD=EF=BF=BD: Invalid=
argument
> ls: ????=EF=BF=BD??=EF=BF=BD.=EF=BF=BDk?: Invalid argument
> ls: ???=EF=BF=BD=EF=BF=BD=DD=A8=EF=BF=BD.fA?: Invalid argument
> ls: ??=EF=BF=BD=EF=BF=BD5=EF=BF=BD?z.=EF=BF=BD?=EF=BF=BD: Invalid argumen=
t
> ls: ??=EF=BF=BDm?=EF=BF=BD!?.`??: Invalid argument
> ls: ??=EF=BF=BD?0%=EF=BF=BD=EF=BF=BD.:=EF=BF=BD?: Invalid argument
> ls: ??=EF=BF=BD?=EF=BF=BD?=EF=BF=BD=EF=BF=BD.=EF=BF=BDf=EF=BF=BD: Invalid=
argument
> ls: ?_=EF=BF=BD?=EF=BF=BD=EF=BF=BD5=EF=BF=BD.??=EF=BF=BD: Invalid argumen=
t
> ls: ?z=EF=BF=BDe=EF=BF=BD>=EF=BF=BDt.8=EF=BF=BDe: Invalid argument
> ls: ?{wk??=EF=BF=BD=EF=BF=BD.=EF=BF=BD??: Invalid argument
> ls: ?=EF=BF=BD?s#"">.=EF=BF=BD=EF=BF=BD=EF=BF=BD: Invalid argument
> ls: ?=EF=BF=BD=EF=BF=BD/=EF=BF=BD=EF=BF=BD0?.=EF=BF=BDf=EF=BF=BD: Invalid=
argument
> ls: ?=EF=BF=BD?K1\K=EF=BF=BD.=EF=BF=BDc?: Invalid argument
> ls: ?=EF=BF=BD=EF=BF=BDc=EF=BF=BD?W=EF=BF=BD.w=EF=BF=BD=EF=BF=BD: Invalid=
argument
> ls: ?=EF=BF=BD=EF=BF=BDeRl?=EF=BF=BD.A?y: Invalid argument
> ls: ?=EF=BF=BD=EF=BF=BD6q=EF=BF=BDog.=EF=BF=BDg): Invalid argument
>
> It happens on different disks which lowers the possibility of hardware
> problem. I think it always involves fuse kernel module (this time I was
> copying files from NTFS drive to FAT32 file. It is not related to rsync
> only as I thought before, because this time files were copied in Thunar
> with copy/paste.
>
> Any tips where should I start looking for souultion would be
> appretiated. Also an advice how to delete these files now (they don't
> even have inode numbers).
>
I think that I've seen similar issues on FAT32 file systems. But I've seem
that only on
a few files and that's not persistant.
Can you first try to identify the problem by testing only on FAT32 and only
on NTFS?
FAT32 should not depend on fuse, only ntfs-3g depends on fuse I think.
> Regards,
> --
> Marko Cupa=C4=87
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
--=20
Cheers,
Henry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEJt7hbd5ORuAa3xnQYjC9GngihYuyuTc9W0AhaDfhr7bkm7zA>