From owner-freebsd-fs@FreeBSD.ORG Mon Sep 22 10:09:16 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 395F016A4B3; Mon, 22 Sep 2003 10:09:16 -0700 (PDT) Received: from mail.ryu16.org (YahooBB219005044040.bbtec.net [219.5.44.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id C796F43FB1; Mon, 22 Sep 2003 10:09:08 -0700 (PDT) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id h8MH94gb078483; Tue, 23 Sep 2003 02:09:04 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id h8MH93xv078482; Tue, 23 Sep 2003 02:09:03 +0900 (JST) (envelope-from imura) Date: Tue, 23 Sep 2003 02:09:03 +0900 From: "R. Imura" To: freebsd-fs@freebsd.org, freebsd-i18n@freebsd.org Message-ID: <20030922170903.GA43754@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i-ja.1 cc: bp@freebsd.org cc: ache@freebsd.org cc: sobomax@freebsd.org Subject: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 17:09:16 -0000 Hi all, I made a patch for multi-byte character extension of three file systems with enhanced LIBICONV in the kernel. File systems are cd9660(joliet part), msdosfs, and ntfs. http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff I believe this will be good news to many of the people, such as Asian using multi-byte characters and others using single-byte characters which FreeBSD doesn't prepare convertion tables yet. Currently it is only limitted to 8 bit ascii characters convertion by LIBICONV or ports/cd9660_unicode or external libdata/msdosfs tables. I extented LIBICONV to handle 16 bit characters and add new kiconv library to generate convertion tables. If iconv(3) has a convertion rule, these file systems can use the rule. (So, ports/cd9660_unicode and libdata/msdosfs will be obsoluted. It also throw ports/{japanese,korean}/msdosfs away.) Here is the summary. New Library - kiconv(3) New Kernel Options (Kernel Modules) - CD9660_ICONV (cd9660_iconv.ko) - MSDOSFS_ICONV (msdosfs_iconv.ko) - NTFS_ICONV (ntfs_iconv.ko) Related Kernel Options (Kernel Modules) - CD9660 (cd9660.ko) - MSDOSFS (msdosfs.ko) - NTFS (ntfs.ko) - LIBICONV (libiconv.ko) Related Port - ports/converters/libiconv For example, with the cd9660 case, the multi-byte character convertion will be enabled when all of CD9660, CD9660_ICONV, and LIBICONV are specified. When only with CD9660, it behaves as before. kiconv(3) uses dlopen(3) to load userland iconv(3) library and generate a character convertion table. Then, copyin(9) the table via sysctl and kernel side iconv(9) uses this table for character convertion. (this is same as existent LIBICONV architecture) If someone has much better idea or kind of enhancement, a thing to do is only replace/add kiconv(3) and iconv(9). Any comments? And is it possible to apply this patch to upcoming FreeBSD-5.2? I tested them with Japanise on i386 machine, and did make release with i386/pc98/alpha/sparc64/ia64/amd64 via cross building. Note that because of bumping MODULE_VERSION of libiconv, kern/56570 must be applied before play with this patch. (loading smbfs will crash your system) P.S. Though it may be very small thing, I think this will be one of a benefit to chose FreeBSD, because many peple (are forced to) live with MS Windows, and this enhancement shorten a distance between FreeBSD and Windows environment. Best Regards, - R. Imura From owner-freebsd-fs@FreeBSD.ORG Tue Sep 23 04:04:21 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9AC016A4B3; Tue, 23 Sep 2003 04:04:21 -0700 (PDT) Received: from mail.ryu16.org (YahooBB219005044040.bbtec.net [219.5.44.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id E92664400B; Tue, 23 Sep 2003 04:04:18 -0700 (PDT) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id h8NB4Ggb019628; Tue, 23 Sep 2003 20:04:16 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id h8NB4GiB019627; Tue, 23 Sep 2003 20:04:16 +0900 (JST) (envelope-from imura) Date: Tue, 23 Sep 2003 20:04:16 +0900 From: "R. Imura" To: freebsd-fs@freebsd.org, freebsd-i18n@freebsd.org Message-ID: <20030923110416.GA16446@ryu16.org> References: <20030922170903.GA43754@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030922170903.GA43754@ryu16.org> User-Agent: Mutt/1.4.1i-ja.1 cc: bp@freebsd.org cc: ache@freebsd.org cc: sobomax@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 11:04:22 -0000 Hi, On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: > I made a patch for multi-byte character extension > of three file systems with enhanced LIBICONV in the > kernel. File systems are cd9660(joliet part), msdosfs, > and ntfs. > > http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff I should tell you one important thing that about 200 Japanese have been using this patch and there aren't any problem reported yet. Regards, - R. Imura From owner-freebsd-fs@FreeBSD.ORG Tue Sep 23 05:02:17 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A827116A4B3; Tue, 23 Sep 2003 05:02:17 -0700 (PDT) Received: from sbtm.yonsei.net (sbtm.yonsei.net [61.100.191.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04BF743FE1; Tue, 23 Sep 2003 05:02:17 -0700 (PDT) (envelope-from perky@sbtm.yonsei.net) Received: by sbtm.yonsei.net (Postfix, from userid 1001) id 08E6F28411; Tue, 23 Sep 2003 21:03:00 +0900 (KST) Date: Tue, 23 Sep 2003 21:02:59 +0900 From: Hye-Shik Chang To: "R. Imura" Message-ID: <20030923120259.GA84509@fallin.lv> References: <20030922170903.GA43754@ryu16.org> <20030923110416.GA16446@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030923110416.GA16446@ryu16.org> Organization: Yonsei University User-Agent: Mutt/1.5.4i cc: freebsd-fs@freebsd.org cc: freebsd-i18n@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 12:02:17 -0000 On Tue, Sep 23, 2003 at 08:04:16PM +0900, R. Imura wrote: > Hi, > > On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: > > I made a patch for multi-byte character extension > > of three file systems with enhanced LIBICONV in the > > kernel. File systems are cd9660(joliet part), msdosfs, > > and ntfs. > > > > http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff > > I should tell you one important thing that about 200 Japanese have > been using this patch and there aren't any problem reported yet. and 1 Korean. Thank you so much!! Hye-Shik =) From owner-freebsd-fs@FreeBSD.ORG Tue Sep 23 05:09:43 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F06B16A4B3; Tue, 23 Sep 2003 05:09:43 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E4DD43F85; Tue, 23 Sep 2003 05:09:41 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.10/8.12.10) with ESMTP id h8NC9eRA029969; Tue, 23 Sep 2003 16:09:40 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.10/8.12.10/Submit) id h8NC9dkq029968; Tue, 23 Sep 2003 16:09:39 +0400 (MSD) (envelope-from ache) Date: Tue, 23 Sep 2003 16:09:38 +0400 From: Andrey Chernov To: "R. Imura" Message-ID: <20030923120936.GA29844@nagual.pp.ru> References: <20030922170903.GA43754@ryu16.org> <20030923110416.GA16446@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030923110416.GA16446@ryu16.org> User-Agent: Mutt/1.5.4i cc: freebsd-fs@freebsd.org cc: bp@freebsd.org cc: sobomax@freebsd.org cc: freebsd-i18n@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 12:09:43 -0000 On Tue, Sep 23, 2003 at 20:04:16 +0900, R. Imura wrote: > Hi, > > On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: > > I made a patch for multi-byte character extension > > of three file systems with enhanced LIBICONV in the > > kernel. File systems are cd9660(joliet part), msdosfs, > > and ntfs. > > > > http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff > > I should tell you one important thing that about 200 Japanese have > been using this patch and there aren't any problem reported yet. All you need at this stage is to find one committer who understand multibyte/asian stuff enough (it is not me) and can integrate this patches into kernel module. I personally don't think it belongs to port, but, rather KLD module, especially if it covers most of Unicode. From owner-freebsd-fs@FreeBSD.ORG Tue Sep 23 05:28:26 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 838DB16A4B3; Tue, 23 Sep 2003 05:28:26 -0700 (PDT) Received: from sbtm.yonsei.net (sbtm.yonsei.net [61.100.191.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA8F443FEC; Tue, 23 Sep 2003 05:28:25 -0700 (PDT) (envelope-from perky@sbtm.yonsei.net) Received: by sbtm.yonsei.net (Postfix, from userid 1001) id E692028411; Tue, 23 Sep 2003 21:29:08 +0900 (KST) Date: Tue, 23 Sep 2003 21:29:08 +0900 From: Hye-Shik Chang To: "R. Imura" Message-ID: <20030923122908.GA84813@fallin.lv> References: <20030922170903.GA43754@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030922170903.GA43754@ryu16.org> Organization: Yonsei University User-Agent: Mutt/1.5.4i cc: freebsd-fs@freebsd.org cc: freebsd-i18n@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 12:28:26 -0000 On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: > Hi all, > > I made a patch for multi-byte character extension > of three file systems with enhanced LIBICONV in the > kernel. File systems are cd9660(joliet part), msdosfs, > and ntfs. > > http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff > [snip] > Related Kernel Options (Kernel Modules) > - CD9660 (cd9660.ko) > - MSDOSFS (msdosfs.ko) I found your patch to sys/fs/msdosfs can become simpler with Darwin's msdosfs modification that gathers a unicode string first and convert it later. I have a UTF-8 hardcoded patch that ported from Darwin to FreeBSD CURRENT. (the patch didn't tested by anybody else than I. :) http://people.freebsd.org/~perky/msdosfs-utf8.diff Regards, Hye-Shik =) From owner-freebsd-fs@FreeBSD.ORG Tue Sep 23 13:24:30 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A3BE16A4B3; Tue, 23 Sep 2003 13:24:30 -0700 (PDT) Received: from baraca.united.net.ua (vlan1.baraca.united.net.ua [195.234.212.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2145B43FBF; Tue, 23 Sep 2003 13:24:28 -0700 (PDT) (envelope-from sobomax@portaone.com) Received: from portaone.com (office-l6-gw.united.net.ua [193.111.8.74]) h8NKNhYu020544; Tue, 23 Sep 2003 23:23:53 +0300 (EEST) (envelope-from sobomax@portaone.com) Message-ID: <3F70ABCF.6030300@portaone.com> Date: Tue, 23 Sep 2003 23:23:43 +0300 From: Maxim Sobolev User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en, ru, uk MIME-Version: 1.0 To: Andrey Chernov References: <20030922170903.GA43754@ryu16.org> <20030923110416.GA16446@ryu16.org> <20030923120936.GA29844@nagual.pp.ru> In-Reply-To: <20030923120936.GA29844@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-fs@FreeBSD.ORG cc: bp@FreeBSD.ORG cc: sobomax@FreeBSD.ORG cc: freebsd-i18n@FreeBSD.ORG Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 20:24:30 -0000 Andrey Chernov wrote: > On Tue, Sep 23, 2003 at 20:04:16 +0900, R. Imura wrote: > >>Hi, >> >>On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: >> >>>I made a patch for multi-byte character extension >>>of three file systems with enhanced LIBICONV in the >>>kernel. File systems are cd9660(joliet part), msdosfs, >>>and ntfs. >>> >>> http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff >> >>I should tell you one important thing that about 200 Japanese have >>been using this patch and there aren't any problem reported yet. > > > All you need at this stage is to find one committer who understand > multibyte/asian stuff enough (it is not me) and can integrate this patches > into kernel module. I personally don't think it belongs to port, but, > rather KLD module, especially if it covers most of Unicode. I agree with Andrey, this patch is something that FreeBSD really needs. -Maxim From owner-freebsd-fs@FreeBSD.ORG Wed Sep 24 08:03:03 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB13716A4BF; Wed, 24 Sep 2003 08:03:03 -0700 (PDT) Received: from mail.ryu16.org (YahooBB219005044040.bbtec.net [219.5.44.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4029343FBD; Wed, 24 Sep 2003 08:02:59 -0700 (PDT) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id h8OF2tgb082820; Thu, 25 Sep 2003 00:02:55 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id h8OF2s2N082819; Thu, 25 Sep 2003 00:02:54 +0900 (JST) (envelope-from imura) Date: Thu, 25 Sep 2003 00:02:54 +0900 From: "R. Imura" To: Andrey Chernov Message-ID: <20030924150254.GA27255@ryu16.org> References: <20030922170903.GA43754@ryu16.org> <20030923110416.GA16446@ryu16.org> <20030923120936.GA29844@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030923120936.GA29844@nagual.pp.ru> User-Agent: Mutt/1.4.1i-ja.1 cc: freebsd-fs@freebsd.org cc: bp@freebsd.org cc: sobomax@freebsd.org cc: freebsd-i18n@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 15:03:04 -0000 On Tue, Sep 23, 2003 at 04:09:38PM +0400, Andrey Chernov wrote: > All you need at this stage is to find one committer who understand > multibyte/asian stuff enough (it is not me) and can integrate this patches Hmm, I don't know who is good at mutlibyte/asian stuff in FreeBSD. Anybody kindly would like to look at this? Or... I know well about Japanese, and little about Korean(KSC5601) and Chinese(Big5, GB2312, but not about GB18030). Though I've once given up committer's work a few years ago, if permitted, I think I can do myself. > into kernel module. I personally don't think it belongs to port, but, > rather KLD module, especially if it covers most of Unicode. It already does, or do you think about something different from me? Unicode convertion part is in libiconv.ko and *_iconv.ko. Regards, - R. Imura From owner-freebsd-fs@FreeBSD.ORG Wed Sep 24 08:09:53 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F8F716A4B3; Wed, 24 Sep 2003 08:09:53 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B70E43FF5; Wed, 24 Sep 2003 08:09:51 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.10/8.12.10) with ESMTP id h8OF9okB030238; Wed, 24 Sep 2003 19:09:50 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.10/8.12.10/Submit) id h8OF9nsd030237; Wed, 24 Sep 2003 19:09:49 +0400 (MSD) (envelope-from ache) Date: Wed, 24 Sep 2003 19:09:46 +0400 From: Andrey Chernov To: "R. Imura" Message-ID: <20030924150944.GA30192@nagual.pp.ru> References: <20030922170903.GA43754@ryu16.org> <20030923110416.GA16446@ryu16.org> <20030923120936.GA29844@nagual.pp.ru> <20030924150254.GA27255@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030924150254.GA27255@ryu16.org> User-Agent: Mutt/1.5.4i cc: freebsd-fs@freebsd.org cc: bp@freebsd.org cc: freebsd-i18n@freebsd.org cc: sobomax@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 15:09:53 -0000 On Thu, Sep 25, 2003 at 00:02:54 +0900, R. Imura wrote: > It already does, or do you think about something different from me? > Unicode convertion part is in libiconv.ko and *_iconv.ko. I mean making cd9660 system KLD and not a port. From owner-freebsd-fs@FreeBSD.ORG Wed Sep 24 09:06:26 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E013D16A4B3; Wed, 24 Sep 2003 09:06:26 -0700 (PDT) Received: from mail.ryu16.org (YahooBB219005044040.bbtec.net [219.5.44.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B5E643FDF; Wed, 24 Sep 2003 09:06:25 -0700 (PDT) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id h8OG6Ogb085355; Thu, 25 Sep 2003 01:06:24 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id h8OG6OUS085354; Thu, 25 Sep 2003 01:06:24 +0900 (JST) (envelope-from imura) Date: Thu, 25 Sep 2003 01:06:23 +0900 From: "R. Imura" To: Andrey Chernov Message-ID: <20030924160623.GB27255@ryu16.org> References: <20030922170903.GA43754@ryu16.org> <20030923110416.GA16446@ryu16.org> <20030923120936.GA29844@nagual.pp.ru> <20030924150254.GA27255@ryu16.org> <20030924150944.GA30192@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030924150944.GA30192@nagual.pp.ru> User-Agent: Mutt/1.4.1i-ja.1 cc: freebsd-fs@freebsd.org cc: bp@freebsd.org cc: freebsd-i18n@freebsd.org cc: sobomax@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 16:06:27 -0000 On Wed, Sep 24, 2003 at 07:09:46PM +0400, Andrey Chernov wrote: > On Thu, Sep 25, 2003 at 00:02:54 +0900, R. Imura wrote: > > > It already does, or do you think about something different from me? > > Unicode convertion part is in libiconv.ko and *_iconv.ko. > > I mean making cd9660 system KLD and not a port. Ah, I understood. Thanks. :) - R. Imura From owner-freebsd-fs@FreeBSD.ORG Wed Sep 24 10:22:42 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D8E516A4B3 for ; Wed, 24 Sep 2003 10:22:42 -0700 (PDT) Received: from muse.csie.ntu.edu.tw (muse.csie.ntu.edu.tw [140.112.28.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DCDC43FA3 for ; Wed, 24 Sep 2003 10:22:41 -0700 (PDT) (envelope-from rafan@muse.csie.ntu.edu.tw) Received: by muse.csie.ntu.edu.tw (Postfix, from userid 1001) id 1840552EFF; Thu, 25 Sep 2003 01:22:37 +0800 (CST) Date: Thu, 25 Sep 2003 01:22:37 +0800 From: Rong-en Fan To: fs@freebsd.org Message-ID: <20030924172237.GA95815@muse.csie.ntu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: NFS incorrectly update atime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 17:22:42 -0000 Hi, I'm using FreeBSD 4.8-RELEASE for both NFS server and client, however when i append file from client, it updates both atime and mtime, where atime shouldn't be updated. $ touch testfile $ stat testfile Access: Thu Sep 25 01:17:43 2003 Modify: Thu Sep 25 01:17:43 2003 Change: Thu Sep 25 01:17:43 2003 $ echo foobar >> testfile $ stat testfile Access: Thu Sep 25 01:17:43 2003 Modify: Thu Sep 25 01:19:15 2003 Change: Thu Sep 25 01:19:15 2003 $ echo foobar >> testfile $ stat testfile Access: Thu Sep 25 01:19:31 2003 Modify: Thu Sep 25 01:19:31 2003 Change: Thu Sep 25 01:19:31 2003 it only occur when file is not empty, also i've noticed that http://www.freebsd.org/cgi/query-pr.cgi?pr=44580 is the same problem. BTW, i also test it on 5.1-RELEASE, and got the same result. btw, i don't subscribe this mailing, so please CC me thanks :) Regards, Rong-en Fan From owner-freebsd-fs@FreeBSD.ORG Wed Sep 24 16:05:07 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B15616A4B3 for ; Wed, 24 Sep 2003 16:05:07 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 328B344017 for ; Wed, 24 Sep 2003 16:05:06 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id JAA09575; Thu, 25 Sep 2003 09:04:39 +1000 Date: Thu, 25 Sep 2003 09:03:08 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Rong-en Fan In-Reply-To: <20030924172237.GA95815@muse.csie.ntu.edu.tw> Message-ID: <20030925084707.T5088@gamplex.bde.org> References: <20030924172237.GA95815@muse.csie.ntu.edu.tw> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: fs@freebsd.org Subject: Re: NFS incorrectly update atime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 23:05:07 -0000 On Thu, 25 Sep 2003, Rong-en Fan wrote: > I'm using FreeBSD 4.8-RELEASE for both NFS server and client, > however when i append file from client, it updates both > atime and mtime, where atime shouldn't be updated. > > $ touch testfile > $ stat testfile > Access: Thu Sep 25 01:17:43 2003 > Modify: Thu Sep 25 01:17:43 2003 > Change: Thu Sep 25 01:17:43 2003 > $ echo foobar >> testfile > $ stat testfile > Access: Thu Sep 25 01:17:43 2003 > Modify: Thu Sep 25 01:19:15 2003 > Change: Thu Sep 25 01:19:15 2003 > $ echo foobar >> testfile > $ stat testfile > Access: Thu Sep 25 01:19:31 2003 > Modify: Thu Sep 25 01:19:31 2003 > Change: Thu Sep 25 01:19:31 2003 This still happens in -current. I think it is normal nfs brokenness... > it only occur when file is not empty, also i've noticed that Writes to 8K boundaries also don't update the atime. I tried "dd if=/dev/zero of=8k count=1 >>foobar". 8K is my server's filesystem block size. I'm not sure if this magic number is for the server or nfs-related. I think the client just does a read as part of a read-modify-write. It works with blocks, so it must do a read before write in all cases where the write is not on a block boundary, and at least FreeBSD ffs servers have no way to avoid updating the atime on read short of a global mount -noatime. Some of the reads, including ones from small test files in your example, may be from a client cache, so the atime update might be avoided accidentally, but a read will always be necessay if the cache is cold. > http://www.freebsd.org/cgi/query-pr.cgi?pr=44580 > is the same problem. BTW, i also test it on 5.1-RELEASE, > and got the same result. This was misclassified in the "i386" category where it is hard to see (unfortunately there is an i386 mailing list which seems to have no activity except for blackholing i386 PRs). It has nothing to do with i386's, so I moved it to the "kern" category. gnats seems to be broken -- didn't prompt for a reason. Bruce From owner-freebsd-fs@FreeBSD.ORG Thu Sep 25 05:20:06 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2863516A4B3 for ; Thu, 25 Sep 2003 05:20:06 -0700 (PDT) Received: from muse.csie.ntu.edu.tw (muse.csie.ntu.edu.tw [140.112.28.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D1F4400E for ; Thu, 25 Sep 2003 05:20:05 -0700 (PDT) (envelope-from rafan@muse.csie.ntu.edu.tw) Received: by muse.csie.ntu.edu.tw (Postfix, from userid 1001) id B867452EFF; Thu, 25 Sep 2003 20:20:04 +0800 (CST) From: Rong-en Fan To: bde@zeta.org.au (Bruce Evans) In-Reply-To: X-Newsgroups: mailing.freebsd.fs User-Agent: tin/1.6.1-20030810 ("Mingulay") (UNIX) (FreeBSD/4.8-RELEASE-p4 (i386)) Message-Id: <20030925122004.B867452EFF@muse.csie.ntu.edu.tw> Date: Thu, 25 Sep 2003 20:20:04 +0800 (CST) cc: fs@freebsd.org Subject: Re: NFS incorrectly update atime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2003 12:20:06 -0000 In article you wrote: > >> it only occur when file is not empty, also i've noticed that > > I think the client just does a read as part of a read-modify-write. > It works with blocks, so it must do a read before write in all cases where > the write is not on a block boundary, and at least FreeBSD ffs servers > have no way to avoid updating the atime on read short of a global mount > -noatime. Some of the reads, including ones from small test files in your > example, may be from a client cache, so the atime update might be avoided > accidentally, but a read will always be necessay if the cache is cold. My application is NFS mail spool, so atime is important to me. I've tested it on Linux client, it's atime not updated in this case. So, I don't know if we can fix this or any workaround? From owner-freebsd-fs@FreeBSD.ORG Thu Sep 25 09:39:59 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E84E516A4B3 for ; Thu, 25 Sep 2003 09:39:59 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EA1343FAF for ; Thu, 25 Sep 2003 09:39:59 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 627DD72DA3; Thu, 25 Sep 2003 09:39:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 602F372DA2; Thu, 25 Sep 2003 09:39:59 -0700 (PDT) Date: Thu, 25 Sep 2003 09:39:59 -0700 (PDT) From: Doug White To: Rong-en Fan In-Reply-To: <20030925122004.B867452EFF@muse.csie.ntu.edu.tw> Message-ID: <20030925093901.H8717@carver.gumbysoft.com> References: <20030925122004.B867452EFF@muse.csie.ntu.edu.tw> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: fs@freebsd.org Subject: Re: NFS incorrectly update atime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2003 16:40:00 -0000 On Thu, 25 Sep 2003, Rong-en Fan wrote: > My application is NFS mail spool, so atime is important to me. > I've tested it on Linux client, it's atime not updated in this case. > So, I don't know if we can fix this or any workaround? This is an exceptionally bad idea, unless your application knows it is talking to NFS. There is no locking and sendmail, etc. expect to be able to use file locking to protect queue files from itself. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-fs@FreeBSD.ORG Thu Sep 25 10:10:30 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E24216A4B3 for ; Thu, 25 Sep 2003 10:10:30 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DED9F43FFB for ; Thu, 25 Sep 2003 10:10:28 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h8PHA7gL051411 for ; Thu, 25 Sep 2003 13:10:07 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h8PHA7Pa051408 for ; Thu, 25 Sep 2003 13:10:07 -0400 (EDT) Date: Thu, 25 Sep 2003 13:10:07 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: fs@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Looking for someone to work on NFS advisory locking... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Sep 2003 17:10:30 -0000 FreeBSD 5.x includes an rpc.lockd that is substantially more functional than previous versions at doing distributed locking. Between 5.0 and 5.1, a couple of people worked to resolve some of the outstanding issues in rpc.lockd -- we got a lot of them fixed. However, I'm still running into some substantial problems using rpc.lockd on a daily basis, especially with my crash machines (they like to exercise the locking protocol recovery cases :-). Currently, I'm aware of at least the following problems: (1) rpc.lockd does not handle "aborts" on lock requests. Normally, FreeBSD permits signals to interrupt advisory lock acquisition for local files -- when this happens, the process/thread is simply removed from the list of contenders for the lock when it is released. This is current disabled for NFS locking (no PCATCH in the tsleep) because the kernel code and rpc.lockd have no protocol expression of the notion that a request has been aborted. If PCATCH is added back, the lock request "gets lost" -- i.e., rpc.lockd does acquire the lock on behalf of the process, and then it gets dropped on the floor somewhere where it can't get unlocked. We need to add the ability to express lock request aborts to the kernel<->rpc.lockd protocol. We then need to figure out what to do in rpc.lockd to have the right thing happen with the wire locking protocol. I don't have the NFS locking spec here so I'm not sure what that means. (2) Recovery in the event of a failure is currently problematic. The kernel maintains no state about what locks are held; rpc.lockd does maintain state but reacts poorly in the event of an unexpected wire message. This is especially visible in the context of (1) above: if rpc.lockd gets a lock grant it doesn't expect, it appears to drop it and never release the lock. I haven't comfirmed the details here. If you kill rpc.lockd and restart it, you're hosed. (3) There may be a problem in involving rpc.statd: on a reboot of the client while holding a lock, the lock never appears to be released on the server, so when the client boots up and tries to grab it (i.e., a mail queue lock), the client will wait forever. I don't currently have time to chase down these issues, although I can reproduce a number pretty easily. I was wondering if anyone out there wants to try and grab rpc.lockd by its horns and attempt to address some of these. In the past, Alfred has suggested that the right answer for the state management issue may be to move the NFS locking state machines into the kernel, which would at least eliminate the issue of synchronizing kernel and rpc.lockd state. On the other hand, it might make integration with rpc.statd harder, as well as perhaps make it harder to debug or implement. In any case, we do need to work on this more, so qualified volunteers would be welcome :-). I also suspect we need to do more in the way of interop testing with other locking implementations -- specifically, the Linux implementation. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories From owner-freebsd-fs@FreeBSD.ORG Thu Sep 25 17:07:07 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDEAE16A4B3 for ; Thu, 25 Sep 2003 17:07:07 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6260744035 for ; Thu, 25 Sep 2003 17:07:06 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id KAA13883; Fri, 26 Sep 2003 10:06:34 +1000 Date: Fri, 26 Sep 2003 10:05:12 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Doug White In-Reply-To: <20030925093901.H8717@carver.gumbysoft.com> Message-ID: <20030926094804.X12230@gamplex.bde.org> References: <20030925122004.B867452EFF@muse.csie.ntu.edu.tw> <20030925093901.H8717@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Rong-en Fan cc: fs@freebsd.org Subject: Re: NFS incorrectly update atime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 00:07:07 -0000 On Thu, 25 Sep 2003, Doug White wrote: > On Thu, 25 Sep 2003, Rong-en Fan wrote: > > > My application is NFS mail spool, so atime is important to me. > > I've tested it on Linux client, it's atime not updated in this case. > > So, I don't know if we can fix this or any workaround? I think it is not easy to fix or work around. Linux has timestamping at a higher level, so I think low-level i/o's done by nfs would avoid it without really trying, leaving the problem of making the client tell the server when to do the updates. I'm not very familiar with nfs's protocols for metadata, but seem to remember that none are used for atime updates for reads of data that has been cached by the client, and that this is important for efficiency. So atime updates are fundamentally broken for nfs. > This is an exceptionally bad idea, unless your application knows it is > talking to NFS. There is no locking and sendmail, etc. expect to be able > to use file locking to protect queue files from itself. There is nfs locking in -current. Bruce From owner-freebsd-fs@FreeBSD.ORG Fri Sep 26 03:31:04 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7EB916A4B3; Fri, 26 Sep 2003 03:31:04 -0700 (PDT) Received: from relay.butya.kz (butya-gw.butya.kz [212.19.129.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9C2F43FDF; Fri, 26 Sep 2003 03:31:01 -0700 (PDT) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 42C095935; Fri, 26 Sep 2003 17:30:56 +0700 (ALMST) Date: Fri, 26 Sep 2003 17:30:55 +0700 From: Boris Popov To: "R. Imura" Message-ID: <20030926103055.GD48438@vertex.kz> References: <20030922170903.GA43754@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030922170903.GA43754@ryu16.org> User-Agent: Mutt/1.4.1i cc: freebsd-fs@freebsd.org cc: sobomax@freebsd.org cc: freebsd-i18n@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 10:31:05 -0000 On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: > > I made a patch for multi-byte character extension > of three file systems with enhanced LIBICONV in the > kernel. File systems are cd9660(joliet part), msdosfs, > and ntfs. Great work, I should say! The patch itself looks good. There is only one minor note: function iconv_vfs_refcount() looks like misplaced one. It doesn't really belong to the iconv module and pollutes it with mount.h. May be getting this function into one of vfs_*.c files would be a better idea, although I'm don't have strong opinion on that. > > New Kernel Options (Kernel Modules) > - CD9660_ICONV (cd9660_iconv.ko) > - MSDOSFS_ICONV (msdosfs_iconv.ko) > - NTFS_ICONV (ntfs_iconv.ko) *_iconv.ko modules aren't strictly necessary and at some point they could be integrated into corresponding fs modules. libiconv.ko module isn't that large to significantly bloat install floppies. > > Any comments? And is it possible to apply this > patch to upcoming FreeBSD-5.2? I think yes. In addition, it is a good candidate for MFC into RELENG_4. > > P.S. > Though it may be very small thing, No this is great thing, thanks for your work! -- Boris Popov http://rbp.euro.ru From owner-freebsd-fs@FreeBSD.ORG Fri Sep 26 06:25:59 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E54F16A4B3 for ; Fri, 26 Sep 2003 06:25:59 -0700 (PDT) Received: from mail.dtek.chalmers.se (osiris.medic.chalmers.se [129.16.30.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95BB243FF3 for ; Fri, 26 Sep 2003 06:25:57 -0700 (PDT) (envelope-from moro@dtek.chalmers.se) Received: from moro.dtek.chalmers.se (moro.dtek.chalmers.se [129.16.30.44]) by mail.dtek.chalmers.se (Postfix) with ESMTP id 232C53B23B for ; Fri, 26 Sep 2003 15:25:56 +0200 (MEST) Received: by moro.dtek.chalmers.se (Postfix, from userid 133119) id BCF954F88F; Fri, 26 Sep 2003 15:25:55 +0200 (MEST) Received: from localhost (localhost [127.0.0.1]) by moro.dtek.chalmers.se (Postfix) with ESMTP id 8EDF256FEC for ; Fri, 26 Sep 2003 15:25:55 +0200 (MEST) Date: Fri, 26 Sep 2003 15:25:55 +0200 (MEST) From: Stefan Moro To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: mv & NFS problem.. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 13:25:59 -0000 Hello.. I'm running FreeBSD 5.1 on a computer configured as an nfs-client and freebsd4.8 on a computer configured as an nfs-server. When I try to move something from the client to a partition on the server mounted on the client in fstab using mv the client crashes. The server should be working fine since there is no problem when using mv from a FreeBSD4.8 client to the server. Using mv from the server to the client works fine.. I can without any problem access the files on the nfs server, it's just when using mv that the client crashes. Here are some configurations on the client... This line is used in fstab: 192.168.0.1:/usr /server nfs rw 0 0 These options are compiled into the kernel. options NFSCLIENT #Network Filesystem Client options NFS_ROOT #NFS usable as root device, Any help appreciated //stefan From owner-freebsd-fs@FreeBSD.ORG Fri Sep 26 10:41:42 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE98116A4B3; Fri, 26 Sep 2003 10:41:42 -0700 (PDT) Received: from mail.ryu16.org (YahooBB219005044109.bbtec.net [219.5.44.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A2EE43FA3; Fri, 26 Sep 2003 10:41:38 -0700 (PDT) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id h8QHfa29005874; Sat, 27 Sep 2003 02:41:36 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id h8QHfamX005873; Sat, 27 Sep 2003 02:41:36 +0900 (JST) (envelope-from imura) Date: Sat, 27 Sep 2003 02:41:35 +0900 From: "R. Imura" To: freebsd-fs@freebsd.org, freebsd-i18n@freebsd.org Message-ID: <20030926174135.GB3529@ryu16.org> References: <20030922170903.GA43754@ryu16.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030922170903.GA43754@ryu16.org> User-Agent: Mutt/1.4.1i-ja.1 Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 17:41:43 -0000 On Tue, Sep 23, 2003 at 02:09:03AM +0900, R. Imura wrote: > Hi all, > > I made a patch for multi-byte character extension > of three file systems with enhanced LIBICONV in the > kernel. File systems are cd9660(joliet part), msdosfs, > and ntfs. > > http://www.ryu16.org/FreeBSD/kiconv/kiconv-5_current-20030921.diff I must apologize that www.ryu16.org was unavailable for disk crash, since 9/25 03:00(JST) to 9/27 02:30(JST). (/usr, /var, /home has gone...) Now temporarily recovered. I must replace my machine with new one completely... (It's notebook.) - R. Imura From owner-freebsd-fs@FreeBSD.ORG Fri Sep 26 10:41:53 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18BA716A4B3 for ; Fri, 26 Sep 2003 10:41:53 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2338E44015 for ; Fri, 26 Sep 2003 10:41:52 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0ri.dialup.mindspring.com ([209.86.3.114] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 1A2wbE-0006QV-00; Fri, 26 Sep 2003 10:41:49 -0700 Message-ID: <3F747A32.C407D40F@mindspring.com> Date: Fri, 26 Sep 2003 10:41:06 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Stefan Moro References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4942583874a9b23bedce081689d790e3e93caf27dac41a8fd350badd9bab72f9c350badd9bab72f9c cc: freebsd-fs@freebsd.org Subject: Re: mv & NFS problem.. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 17:41:53 -0000 Stefan Moro wrote: > Hello.. > I'm running FreeBSD 5.1 on a computer configured as an nfs-client and > freebsd4.8 on a computer configured as an nfs-server. When I try to move > something from the client to a partition on the server mounted on the > client in fstab using mv the client crashes. The server should be working > fine since there is no problem when using mv from a FreeBSD4.8 client to > the server. > > Using mv from the server to the client works fine.. What happens if you use "cp" or "dd" instead to copy the file from the client to the server? There are some very different code paths that get exercised by the 3, and it would be useful to know whether it's the explicit write path, the page fault write path, the explicit read path, the page fault read path, or some combination of the 4 that result in the error. Using the 'cp' and 'dd' approach, you would eliminate/implicate 3 of the code paths (given your existing results with 'mv'). -- Terry From owner-freebsd-fs@FreeBSD.ORG Sat Sep 27 05:25:09 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9CDA16A4B3; Sat, 27 Sep 2003 05:25:09 -0700 (PDT) Received: from mail.ryu16.org (YahooBB219005044109.bbtec.net [219.5.44.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4FCE43FDF; Sat, 27 Sep 2003 05:25:04 -0700 (PDT) (envelope-from imura@ryu16.org) Received: from redeye.xt.ryu16.org (localhost [127.0.0.1]) by mail.ryu16.org (8.12.9p1/8.12.9) with ESMTP id h8RCP2wN013193; Sat, 27 Sep 2003 21:25:02 +0900 (JST) (envelope-from imura@redeye.xt.ryu16.org) Received: (from imura@localhost) by redeye.xt.ryu16.org (8.12.9p1/8.12.9/Submit) id h8RCP2HE013192; Sat, 27 Sep 2003 21:25:02 +0900 (JST) (envelope-from imura) Date: Sat, 27 Sep 2003 21:25:02 +0900 From: "R. Imura" To: Boris Popov Message-ID: <20030927122502.GA8470@ryu16.org> References: <20030922170903.GA43754@ryu16.org> <20030926103055.GD48438@vertex.kz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030926103055.GD48438@vertex.kz> User-Agent: Mutt/1.4.1i-ja.1 cc: freebsd-fs@freebsd.org cc: sobomax@freebsd.org cc: freebsd-i18n@freebsd.org Subject: Re: [Patch] cd9660/msdosfs/ntfs/libiconv mutli-byte extention X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2003 12:25:10 -0000 Hi, On Fri, Sep 26, 2003 at 05:30:55PM +0700, Boris Popov wrote: > *_iconv.ko modules aren't strictly necessary and at some point > they could be integrated into corresponding fs modules. libiconv.ko module > isn't that large to significantly bloat install floppies. I don't like this idea, because this means GENERIC kernel has libiconv.ko. > I think yes. In addition, it is a good candidate for MFC into RELENG_4. I think there is a difficulty problem to MFC into RELENG_4. Since DYNAMICROOT is unavailable with RELENG_4, mount_cd9660 will not work w/o /usr. Maybe some knobs should be made to switch dynamic/static linking mount_cd9660/mount_msdosfs/mount_ntfs, and default is statically linked. A patch for RELENG_4 is here: (fjoe's fix should be feeded back, but not yet.) http://www.ryu16.org/FreeBSD/kiconv/kiconv-4_stable-20030911.diff Regards, - R. Imura From owner-freebsd-fs@FreeBSD.ORG Sat Sep 27 10:32:27 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DB7816A4B3 for ; Sat, 27 Sep 2003 10:32:27 -0700 (PDT) Received: from mail.dtek.chalmers.se (osiris.medic.chalmers.se [129.16.30.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4498144030 for ; Sat, 27 Sep 2003 10:32:26 -0700 (PDT) (envelope-from moro@dtek.chalmers.se) Received: from moro.dtek.chalmers.se (moro.dtek.chalmers.se [129.16.30.44]) by mail.dtek.chalmers.se (Postfix) with ESMTP id D93423B27D; Sat, 27 Sep 2003 19:32:24 +0200 (MEST) Received: by moro.dtek.chalmers.se (Postfix, from userid 133119) id 8B4394F88F; Sat, 27 Sep 2003 19:32:24 +0200 (MEST) Received: from localhost (localhost [127.0.0.1]) by moro.dtek.chalmers.se (Postfix) with ESMTP id 610BF56FEC; Sat, 27 Sep 2003 19:32:24 +0200 (MEST) Date: Sat, 27 Sep 2003 19:32:24 +0200 (MEST) From: Stefan Moro To: Terry Lambert In-Reply-To: <3F747A32.C407D40F@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-fs@freebsd.org Subject: Re: mv & NFS problem.. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Sep 2003 17:32:27 -0000 On Fri, 26 Sep 2003, Terry Lambert wrote: > Stefan Moro wrote: > > Hello.. > > I'm running FreeBSD 5.1 on a computer configured as an nfs-client and > > freebsd4.8 on a computer configured as an nfs-server. When I try to move > > something from the client to a partition on the server mounted on the > > client in fstab using mv the client crashes. The server should be working > > fine since there is no problem when using mv from a FreeBSD4.8 client to > > the server. > > > > Using mv from the server to the client works fine.. > > What happens if you use "cp" or "dd" instead to copy the file > from the client to the server? There are some very different > code paths that get exercised by the 3, and it would be useful > to know whether it's the explicit write path, the page fault > write path, the explicit read path, the page fault read path, > or some combination of the 4 that result in the error. > > Using the 'cp' and 'dd' approach, you would eliminate/implicate > 3 of the code paths (given your existing results with 'mv'). > > -- Terry Now I've tried the 'cp' and 'dd' approach with no success.. Both approaches reulted in the client crashing and rebooting. Something that makes this problem even more difficult to understand is that I have managed to use mv two times with success.. Could it be something wrong with my Network adapter??? It's an SMC card using the dc0 driver. I've had this problem before running freebsd4.7 on the client, but I think the problem that time was that the kernel was built from another CVS-release than the rest of the OS. If there are any logs that could be of interest, tell me and I'll post them.. regards Stefan From owner-freebsd-fs@FreeBSD.ORG Sat Sep 27 20:29:17 2003 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ED8A16A4B3; Sat, 27 Sep 2003 20:29:17 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74D824402B; Sat, 27 Sep 2003 20:29:15 -0700 (PDT) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id h8S3TEkL023461; Sat, 27 Sep 2003 23:29:14 -0400 (EDT) (envelope-from winter@jurai.net) Date: Sat, 27 Sep 2003 23:29:14 -0400 (EDT) From: "Matthew N. Dodd" To: Yar Tikhiy In-Reply-To: <20030325125620.GD27905@comp.chem.msu.su> Message-ID: <20030927232851.S35442@sasami.jurai.net> References: <20030322151656.GA34184@comp.chem.msu.su> <20030322211504.X8716@sasami.jurai.net> <20030324225320.B96310@iclub.nsu.ru> <20030324131809.E39864@sasami.jurai.net> <20030325125620.GD27905@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: fs@FreeBSD.ORG Subject: Re: HFS/HFS Plus driver and tools for 5.x are available X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2003 03:29:17 -0000 On Tue, 25 Mar 2003, Yar Tikhiy wrote: > Since introducing a new file system won't disrupt any existing > functionality, this code will be committed to -CURRENT as soon as we > reach an agreement with Apple on the licensing issue. Although APSL > allows us to use this code today, it would be better if Apple moved it > to the BSD license; and there is hope it's possible. Any status update on this matter? Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever |