From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Jun 14 13:50:38 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1142E16A4CE for ; Mon, 14 Jun 2004 13:50:38 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09B9843D5A for ; Mon, 14 Jun 2004 13:50:38 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i5EDoMAj093957 for ; Mon, 14 Jun 2004 13:50:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5EDoMqs093956; Mon, 14 Jun 2004 13:50:22 GMT (envelope-from gnats) Date: Mon, 14 Jun 2004 13:50:22 GMT Message-Id: <200406141350.i5EDoMqs093956@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: "Val P" Subject: RE: ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File corruption X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Val P List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 13:50:38 -0000 The following reply was made to PR ports/67721; it has been noted by GNATS. From: "Val P" To: "'Patrick Dung'" , Cc: Subject: RE: ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File corruption Date: Mon, 14 Jun 2004 08:37:41 -0500 This is a multi-part message in MIME format. ------=_NextPart_000_01C0_01C451EA.DC5E4820 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable =20 The old Fat-32 bug report which says basically the same thing has been = opened in the database for 2 years. Either the bug exists in stable too, or the bug has never been closed. At least I think it's saying the same = thing, you may want to verify. Regardless, I was hoping that 5.x will go = stable sometime soon, so the bug would need to be fixed ;) =20 =20 See http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/39043 for the bug = report that's been open for 2 years. =20 =20 thanks, -val =20 _____ =20 From: Patrick Dung [mailto:patrick_dkt@yahoo.com.hk]=20 Sent: Monday, June 14, 2004 7:39 AM To: Val P; freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File = corruption I don't know if the -stable has this bug. =20 I agree with you point that the fix is not acceptable. I can only say that UFS/UFS2 does not have this bug. Val P wrote: "Fix=20 Use UFS2(possibly UFS) as the backend of share instead of Fat32" The "Fix" in this bug report is not acceptable. Sometimes UFS is not an option. FAT32 is a cross-platform file system. UFS is not. Furthermore such a bug should not be in a -stable branch, unless the end user is warned somehow when trying to use it. Do you picture microsoft shipping out Windows XP with a file corruption bug in FAT32 and telling people (after they experience the problem and data loss, not ahead of = time) that their fix is to use NTFS?=20 =E5=80=9F=E9=81=8E=E3=80=81=E4=B8=80=E6=8B=8D=E5=85=A9=E6=95=A3=E3=80=81=E5= =A5=87=E6=B4=9B=E6=9D=8E=E7=B6=AD=E6=96=AF=E5=9B=9E=E4=BF=A1... =E5=85=A8=E6=B8=AF=E6=9C=80=E5=A4=A7=E6=89=8B=E6=A9=9F=E4=B8=8B=E8=BC=89=E4= =B8=AD=E5=BF=83 http://mobile.yahoo.com.hk/ = =20 ------=_NextPart_000_01C0_01C451EA.DC5E4820 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
 
The old Fat-32 bug report=20 which says basically the same thing = has been opened in the database for 2&= nbsp;years. Either the bug exists in stable=  too,
or the = bug has never=20 been closed. At least I think it's saying the same thing, you may want = to=20 verify. Regardless, I was hoping that 5.x will go stable sometime soon, = so the=20 bug would need to be fixed ;)
 
 
See http://w= ww.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/39043 for=20 the bug report that's been open for 2 = years.
 
 
thanks,
-val

 
From: Patrick Dung=20 [mailto:patrick_dkt@yahoo.com.hk]
Sent: Monday, June 14, 2004 = 7:39=20 AM
To: Val P; = freebsd-gnats-submit@FreeBSD.org
Subject: Re:=20 ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File=20 corruption

I don't know if the -stable has this bug.
 
I agree with you point that the fix is not acceptable.
I can only say that UFS/UFS2 does not have this = bug.

Val P=20 <secureplay@sbcglobal.net> wrote:
"Fix=20
Use UFS2(possibly UFS) as the backend of share instead of=20 Fat32"


The "Fix" in this bug report is not acceptable. = Sometimes=20 UFS is not an
option. FAT32 is a cross-platform file system. UFS is = not.

Furthermore such a bug should not be in a -stable branch, = unless=20 the end
user is warned somehow when trying to use it. Do you = picture=20 microsoft
shipping out Windows XP with a file corruption bug in = FAT32 and=20 telling
people (after they experience the problem and data loss, = not ahead=20 of time)
that their fix is to use NTFS?


=E5=80=9F=E9=81=8E=E3=80=81=E4=B8=80=E6=8B=8D=E5=85=A9=E6=95=A3=E3=80=81= =E5=A5=87=E6=B4=9B=E6=9D=8E=E7=B6=AD=E6=96=AF=E5=9B=9E=E4=BF=A1...
= =E5=85=A8=E6=B8=AF=E6=9C=80=E5=A4=A7=E6=89=8B=E6=A9=9F=E4=B8=8B=E8=BC=89=E4= =B8=AD=E5=BF=83
http://mobile.yahoo.com.hk/

= ------=_NextPart_000_01C0_01C451EA.DC5E4820--