ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File corruption

Mon Jun 14 13:50:38 UTC 2004

The following reply was made to PR ports/67721; it has been noted by GNATS.

From: "Val P" <secureplay at sbcglobal.net>
To: "'Patrick Dung'" <patrick_dkt at yahoo.com.hk>,
	<freebsd-gnats-submit at FreeBSD.org>
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 at yahoo.com.hk]=20
 Sent: Monday, June 14, 2004 7:39 AM
 To: Val P; freebsd-gnats-submit at 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 <secureplay at sbcglobal.net> 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/ =
 <http://us.rd.yahoo.com/evt=3D22281/*http://hk.yahoo.com/mail_tagline/?ht=
 tp://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<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
 <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
 <BODY>
 <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
 size=3D2></FONT> </DIV>
 <DIV><SPAN class=3D947113313-14062004></SPAN><FONT face=3DArial><FONT=20
 color=3D#0000ff><FONT =
 size=3D2>The old Fat-32 bug <SPAN=20
 class=3D947113313-14062004>report=20
 </SPAN>which says basically the same thing =
 has been opened in the database for 2&=
 nbsp;years. Either the bug exists in stable=
  too,</FONT></FONT></FONT></DIV>
 <DIV><SPAN class=3D947113313-14062004></SPAN><FONT face=3DArial><FONT=20
 color=3D#0000ff><FONT size=3D2>o<SPAN class=3D947113313-14062004>r 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 ;)</SPAN></FONT></FONT></FONT></DIV>
 <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004></SPAN></FONT></FONT></FONT> </DIV>
 <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004></SPAN></FONT></FONT></FONT> </DIV>
 <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004>See <A=20
 href=3D"http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/39043">http://w=
 ww.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/39043</A> for=20
 the bug report that's been open for 2 =
 years.</SPAN></FONT></FONT></FONT></DIV>
 <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004></SPAN></FONT></FONT></FONT> </DIV>
 <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004></SPAN></FONT></FONT></FONT> </DIV>
 <DIV><SPAN class=3D947113313-14062004></SPAN><FONT face=3DArial><FONT=20
 color=3D#0000ff><FONT size=3D2>t<SPAN=20
 class=3D947113313-14062004>hanks,</SPAN></FONT></FONT></FONT></DIV>
 <DIV><FONT><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004></SPAN></FONT></FONT></FONT><SPAN=20
 class=3D947113313-14062004></SPAN><FONT face=3DArial><FONT =
 color=3D#0000ff><FONT=20
 size=3D2>-<SPAN =
 class=3D947113313-14062004>val</SPAN></FONT></FONT></FONT></DIV>
 <DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
 class=3D947113313-14062004></SPAN></FONT></FONT></FONT><FONT =
 face=3DArial=20
 color=3D#0000ff size=3D2></FONT><BR> </DIV>
 <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
 <HR tabIndex=3D-1>
 <FONT face=3DTahoma size=3D2><B>From:</B> Patrick Dung=20
 [mailto:patrick_dkt at yahoo.com.hk] <BR><B>Sent:</B> Monday, June 14, 2004 =
 7:39=20
 AM<BR><B>To:</B> Val P; =
 freebsd-gnats-submit at FreeBSD.org<BR><B>Subject:</B> Re:=20
 ports/67721: FreeBSD-current + Samba 3.0.4 + FAT32. File=20
 corruption<BR></FONT><BR></DIV>
 <DIV></DIV>
 <DIV>I don't know if the -stable has this bug.</DIV>
 <DIV> </DIV>
 <DIV>I agree with you point that the fix is not acceptable.</DIV>
 <DIV>I can only say that UFS/UFS2 does not have this =
 bug.<BR><BR><B><I>Val P=20
 <secureplay at sbcglobal.net></I></B> wrote:</DIV>
 <BLOCKQUOTE class=3Dreplbq=20
 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px =
 solid">"Fix=20
   <BR>Use UFS2(possibly UFS) as the backend of share instead of=20
   Fat32"<BR><BR><BR>The "Fix" in this bug report is not acceptable. =
 Sometimes=20
   UFS is not an<BR>option. FAT32 is a cross-platform file system. UFS is =

   not.<BR><BR>Furthermore such a bug should not be in a -stable branch, =
 unless=20
   the end<BR>user is warned somehow when trying to use it. Do you =
 picture=20
   microsoft<BR>shipping out Windows XP with a file corruption bug in =
 FAT32 and=20
   telling<BR>people (after they experience the problem and data loss, =
 not ahead=20
   of time)<BR>that their fix is to use NTFS? <BR><BR><BR></BLOCKQUOTE>
 <P>=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...<BR><B>=
 =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</B><BR><A=20
 href=3D"http://us.rd.yahoo.com/evt=3D22281/*http://hk.yahoo.com/mail_tagl=
 ine/?http://mobile.yahoo.com.hk/">http://mobile.yahoo.com.hk/</A><BR></P>=
 </BODY></HTML>

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