Date: Sat, 23 Mar 2013 20:27:07 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Pavel Gorshkov <gorshkov.pavel@gmail.com> Cc: freebsd-current@freebsd.org, Marko Zec <zec@fer.hr> Subject: Re: Report on issues with fusefs Message-ID: <CAN6yY1vZaHtkLv4BWGMz9wYDZcfi04PrRivrnAzB9YtibNbCXw@mail.gmail.com> In-Reply-To: <20130323215236.GA17446@localhost> References: <CAN6yY1vYF=i7%2BgdjX2nYMCzjomhrSRAS1qpBMB7-qo0XSgx0JA@mail.gmail.com> <20130323215236.GA17446@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 23, 2013 at 2:52 PM, Pavel Gorshkov <gorshkov.pavel@gmail.com> wrote: > On Fri, Mar 22, 2013 at 10:16:09PM -0700, Kevin Oberman wrote: >> I've now been using fusefs regularly for a few months and I have found >> a few issues that i wanted to report. >> >> Most disturbing is corrupted NTFS systems. On several occasions I have >> found an NTFS system could not be written to with either FreeBSD or >> Windows. I had to user Windows disk check to repair the file system, >> but a few files were lost. this may be an issue with either fusefs or >> ntfs-3g. Not sure which, but it is likely tied to the next issue. > > This patch, also referenced in ports/169165, might help solve at > least some of the issues: > > http://www.mail-archive.com/freebsd-users-jp@jp.freebsd.org/msg04947.html > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169165 Thanks, Pavel, but my problem has not involved permissions nor does it cause a panic, so while this patch looks reasonable and I suspect it (or something similar) is needed, I don't see how it would fix the problems I am seeing. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vZaHtkLv4BWGMz9wYDZcfi04PrRivrnAzB9YtibNbCXw>