From owner-freebsd-fs@FreeBSD.ORG Mon Jan 10 10:08:41 2005 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 4320116A4CE for ; Mon, 10 Jan 2005 10:08:41 +0000 (GMT) Received: from web30301.mail.mud.yahoo.com (web30301.mail.mud.yahoo.com [68.142.200.94]) by mx1.FreeBSD.org (Postfix) with SMTP id B26A543D46 for ; Mon, 10 Jan 2005 10:08:40 +0000 (GMT) (envelope-from barath_yes@yahoo.com.sg) Received: (qmail 29847 invoked by uid 60001); 10 Jan 2005 10:08:40 -0000 Message-ID: <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com> Received: from [203.118.46.137] by web30301.mail.mud.yahoo.com via HTTP; Mon, 10 Jan 2005 18:08:40 CST Date: Mon, 10 Jan 2005 18:08:40 +0800 (CST) From: Barath S To: Scott Long In-Reply-To: <41E01905.3040200@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: FreeBsd-MailGrp Subject: Re: using mfs of size > 64Mb and system stability 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, 10 Jan 2005 10:08:41 -0000 Initially, I didn't go for swap based fs as I felt that the memory occupied will be from the swap area. As you are saying that the allocation will be from buffer/cache, I will test swap-mfs. Updates on malloc-mfs: System didn't crash when creating malloc based fs with "-o reserve" option for a size of 128Mb. But, when tried creating two mfs(s) each with sizes of 24Mb and 1Mb, the system rebooted itself. I tried this in a system with 1G memory. Another observation is that even with this system w/o "-o reserve", the system hangs immediately with mfs-size > 64Mb. Thanks and regards --- Scott Long wrote: > Using the swap option really is the preferred > method. The available > kernel malloc pool is limited and is scaled on the > amount of system > RAM that you have; on my 256MB laptop, it's > reporting only 85MB > available for kernel malloc. So this would explain > why trying to > malloc 128MB for md could fail =-). > > With the swap option, pages are allocated from the > buffer/cache and > held there. They are only swapped to disk when the > system is under > memory pressure, otherwise they stay in RAM. > > Scott > > Barath S wrote: > > Thank you Arne. > > I didn't try with 'swap' option as my requirement > is > > to have the files in memory. I will test with 5.3 > and > > see it that works. > > regards > > --- Arne Wörner wrote: > > > >>--- Barath S wrote: > >> > >>>My intention is create a file system in memory of > >> > >>size > >> > >>>>128Mb and use that for my application. But, I > >>> > >>>couldn't do that as my system hangs whenever I > >> > >>create > >> > >>>a mfs of size > 64Mb. I did the following... > >>> > >>>a) Configured memory file system of size 128Mb > >> > >>using > >> > >>>'mdmfs' command with 'malloc' option. When I > tried > >> > >>to > >> > >>>copy files to this mfs, m/c hanged after copying > >> > >>some > >> > >>>files. > >>>b) Then I rebooted by m/c and configured memory > >> > >>file > >> > >>>system of size 64Mb and this time the copying > >>>operation was successful > >>>c) I observed that the system hanged whenever I > >>>configure a mfs of size > 64Mb and used that mfs > >>> > >>>a) Can someone provide me hints on what could be > >> > >>the > >> > >>>problem ? > >>> > >> > >>I use R5.3. According to the man page mdconfig(8) > a > >>md of type > >>malloc should use "-o reserve", if it is large and > >>to be "filled" > >>(I think the man page means "filled quickly"): > >> "If the -o reserve option is not set, creating > and > >>filling > >> a large malloc-backed memory disk is a very > easy > >>way to > >> panic a system." > >> > >>Maybe that helps? > >> > >>Did you try type "swap"? > >> > >>-Arne > >> > >> > >> > >> > >>__________________________________ > >>Do you Yahoo!? > >>The all-new My Yahoo! - Get yours free! > >>http://my.yahoo.com > >> > >> > >> > > > > > > __________________________________________________ > > Do You Yahoo!? > > Download the latest ringtones, games, and more! > > http://sg.mobile.yahoo.com > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to > "freebsd-fs-unsubscribe@freebsd.org" > > __________________________________________________ Do You Yahoo!? Download the latest ringtones, games, and more! http://sg.mobile.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Mon Jan 10 10:11:46 2005 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 4740216A4CE; Mon, 10 Jan 2005 10:11:46 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87CD343D2D; Mon, 10 Jan 2005 10:11:45 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0AABiWC041248; Mon, 10 Jan 2005 11:11:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Barath S From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 10 Jan 2005 18:08:40 +0800." <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com> Date: Mon, 10 Jan 2005 11:11:44 +0100 Message-ID: <41247.1105351904@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: FreeBsd-MailGrp cc: Scott Long Subject: Re: using mfs of size > 64Mb and system stability 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, 10 Jan 2005 10:11:46 -0000 In message <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com>, Barath S w rites: >Initially, I didn't go for swap based fs as I felt >that the memory occupied will be from the swap area. >As you are saying that the allocation will be from >buffer/cache, I will test swap-mfs. malloc backing should not be used for large disks. If you _truly_ want to have a large disk which is memory backed, you should consider using the "preload" backing as this will withdraw the memory entirely from the kernels use. In general, the benefit from using RAM disks is much smaller than most people realize. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@FreeBSD.ORG Mon Jan 10 13:57:57 2005 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 7D56B16A4CE; Mon, 10 Jan 2005 13:57:57 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCB2343D2D; Mon, 10 Jan 2005 13:57:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 54A1951445; Mon, 10 Jan 2005 05:57:47 -0800 (PST) Date: Mon, 10 Jan 2005 05:57:47 -0800 From: Kris Kennaway To: Poul-Henning Kamp Message-ID: <20050110135747.GA44905@xor.obsecurity.org> References: <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com> <41247.1105351904@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <41247.1105351904@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i cc: FreeBsd-MailGrp cc: Scott Long Subject: Re: using mfs of size > 64Mb and system stability 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, 10 Jan 2005 13:57:57 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 10, 2005 at 11:11:44AM +0100, Poul-Henning Kamp wrote: > In message <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com>, Bara= th S w > rites: > >Initially, I didn't go for swap based fs as I felt > >that the memory occupied will be from the swap area. > >As you are saying that the allocation will be from > >buffer/cache, I will test swap-mfs. >=20 > malloc backing should not be used for large disks. >=20 > If you _truly_ want to have a large disk which is memory backed, > you should consider using the "preload" backing as this will withdraw > the memory entirely from the kernels use. >=20 > In general, the benefit from using RAM disks is much smaller than > most people realize. I've found that using a swap-backed disk substantially cuts back on disk accesses for my purposes (package building, where everything that hits disk will be deleted again in a few minutes). It appears to give a reasonable performance boost, which I'm still trying to measure. Unfortunately, swap-backed md under 6.x deadlocks under some conditions which are being investigated. Kris --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB4onbWry0BWjoQKURAoRMAKDe4IyajL2SoKlKR+PvJBMS3gaeWwCg8vm8 Gq8hke7Io29IXodGpr1RQn4= =FgCB -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From owner-freebsd-fs@FreeBSD.ORG Mon Jan 10 14:03:12 2005 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 8336716A4CE; Mon, 10 Jan 2005 14:03:12 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBA9243D2F; Mon, 10 Jan 2005 14:03:11 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0AE3AKJ045045; Mon, 10 Jan 2005 15:03:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kris Kennaway From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 10 Jan 2005 05:57:47 PST." <20050110135747.GA44905@xor.obsecurity.org> Date: Mon, 10 Jan 2005 15:03:10 +0100 Message-ID: <45044.1105365790@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: FreeBsd-MailGrp cc: Scott Long Subject: Re: using mfs of size > 64Mb and system stability 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, 10 Jan 2005 14:03:12 -0000 In message <20050110135747.GA44905@xor.obsecurity.org>, Kris Kennaway writes: > >--HlL+5n6rz5pIUxbD >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Mon, Jan 10, 2005 at 11:11:44AM +0100, Poul-Henning Kamp wrote: >> In message <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com>, Bara= >th S w >> rites: >> >Initially, I didn't go for swap based fs as I felt >> >that the memory occupied will be from the swap area. >> >As you are saying that the allocation will be from >> >buffer/cache, I will test swap-mfs. >>=20 >> malloc backing should not be used for large disks. >>=20 >> If you _truly_ want to have a large disk which is memory backed, >> you should consider using the "preload" backing as this will withdraw >> the memory entirely from the kernels use. >>=20 >> In general, the benefit from using RAM disks is much smaller than >> most people realize. > >I've found that using a swap-backed disk substantially cuts back on >disk accesses for my purposes [...] Swap-backing is very different from RAM disks in that things get pushed out of RAM if better use can be made of the pages. With RAM disks (preload or malloc backing) you occupy valuable RAM pages with free diskblocks. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@FreeBSD.ORG Tue Jan 11 02:01:37 2005 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 8998216A4D0 for ; Tue, 11 Jan 2005 02:01:37 +0000 (GMT) Received: from web30305.mail.mud.yahoo.com (web30305.mail.mud.yahoo.com [68.142.200.98]) by mx1.FreeBSD.org (Postfix) with SMTP id 2FD5943D39 for ; Tue, 11 Jan 2005 02:01:37 +0000 (GMT) (envelope-from barath_yes@yahoo.com.sg) Received: (qmail 57584 invoked by uid 60001); 11 Jan 2005 02:01:36 -0000 Message-ID: <20050111020136.57582.qmail@web30305.mail.mud.yahoo.com> Received: from [203.118.46.137] by web30305.mail.mud.yahoo.com via HTTP; Tue, 11 Jan 2005 10:01:36 CST Date: Tue, 11 Jan 2005 10:01:36 +0800 (CST) From: Barath S To: Poul-Henning Kamp , Kris Kennaway In-Reply-To: <45044.1105365790@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: FreeBsd-MailGrp cc: Scott Long Subject: Re: using mfs of size > 64Mb and system stability 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, 11 Jan 2005 02:01:37 -0000 Where can I get details regarding the 'preload' backed ram disks ?. How is it different from "malloc" based ram disks? As per 'man mdconfig', there is no such option available. Could you kindly provide me more hints on this? Thanks --- Poul-Henning Kamp wrote: > In message > <20050110135747.GA44905@xor.obsecurity.org>, Kris > Kennaway writes: > > > >--HlL+5n6rz5pIUxbD > >Content-Type: text/plain; charset=us-ascii > >Content-Disposition: inline > >Content-Transfer-Encoding: quoted-printable > > > >On Mon, Jan 10, 2005 at 11:11:44AM +0100, > Poul-Henning Kamp wrote: > >> In message > <20050110100840.29845.qmail@web30301.mail.mud.yahoo.com>, > Bara= > >th S w > >> rites: > >> >Initially, I didn't go for swap based fs as I > felt > >> >that the memory occupied will be from the swap > area. > >> >As you are saying that the allocation will be > from > >> >buffer/cache, I will test swap-mfs. > >>=20 > >> malloc backing should not be used for large > disks. > >>=20 > >> If you _truly_ want to have a large disk which is > memory backed, > >> you should consider using the "preload" backing > as this will withdraw > >> the memory entirely from the kernels use. > >>=20 > >> In general, the benefit from using RAM disks is > much smaller than > >> most people realize. > > > >I've found that using a swap-backed disk > substantially cuts back on > >disk accesses for my purposes [...] > > Swap-backing is very different from RAM disks in > that things get > pushed out of RAM if better use can be made of the > pages. > > With RAM disks (preload or malloc backing) you > occupy valuable > RAM pages with free diskblocks. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be > explained by incompetence. > __________________________________________________ Do You Yahoo!? Download the latest ringtones, games, and more! http://sg.mobile.yahoo.com From owner-freebsd-fs@FreeBSD.ORG Tue Jan 11 06:30:01 2005 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 C3DF216A4CE; Tue, 11 Jan 2005 06:30:01 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB7643D1F; Tue, 11 Jan 2005 06:30:00 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0B6Txj5009327; Tue, 11 Jan 2005 07:29:59 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Barath S From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 11 Jan 2005 10:01:36 +0800." <20050111020136.57582.qmail@web30305.mail.mud.yahoo.com> Date: Tue, 11 Jan 2005 07:29:59 +0100 Message-ID: <9326.1105424999@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: FreeBsd-MailGrp cc: Scott Long cc: Kris Kennaway Subject: Re: using mfs of size > 64Mb and system stability 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, 11 Jan 2005 06:30:01 -0000 In message <20050111020136.57582.qmail@web30305.mail.mud.yahoo.com>, Barath S w rites: >Where can I get details regarding the 'preload' backed > ram disks ?. How is it different from "malloc" based >ram disks? As per 'man mdconfig', there is no such >option available. > >Could you kindly provide me more hints on this? With a preloaded disk you load the disk image from the loader (along with loading the kernel) and the md(4) driver discovers the image automatically. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@FreeBSD.ORG Tue Jan 11 11:27:18 2005 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 02F5A16A4CE for ; Tue, 11 Jan 2005 11:27:18 +0000 (GMT) Received: from feith1.FEITH.COM (feith1.FEITH.COM [192.251.93.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E75D43D2F for ; Tue, 11 Jan 2005 11:27:17 +0000 (GMT) (envelope-from john@feith.com) Received: from jwlab.FEITH.COM (jwlab.FEITH.COM [192.251.93.16]) by feith1.FEITH.COM (8.12.10+Sun/8.12.9) with ESMTP id j0BBRFrt002024 for ; Tue, 11 Jan 2005 06:27:15 -0500 (EST) Received: from jwlab.FEITH.COM (localhost [127.0.0.1]) by jwlab.FEITH.COM (8.12.10+Sun/8.12.10) with ESMTP id j0BBRFLW017164 for ; Tue, 11 Jan 2005 06:27:15 -0500 (EST) Received: (from john@localhost) by jwlab.FEITH.COM (8.12.10+Sun/8.12.10/Submit) id j0BBRFY9017163 for freebsd-fs@freebsd.org; Tue, 11 Jan 2005 06:27:15 -0500 (EST) Date: Tue, 11 Jan 2005 06:27:15 -0500 (EST) From: John Wehle Message-Id: <200501111127.j0BBRFY9017163@jwlab.FEITH.COM> To: freebsd-fs@freebsd.org Content-Type: text X-Scanned-By: MIMEDefang 2.48 on 192.251.93.1 X-Archived: cashew.FEITH.COM Subject: FreeBSD 5.3 Patch to fix udf large files and reading past EOF 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, 11 Jan 2005 11:27:18 -0000 Currently reading udf files > 2 GB is busted due to truncation in the kernel. Also reading a UDF file can return more data than present in the file due to a failure to check the number of bytes being requested with the number of bytes left in the file. Both problems are addressed by the enclosed patch. -- John Wehle ------------------8<------------------------8<------------------------ *** fs/udf/udf_vnops.c.ORIGINAL Sat Oct 2 01:48:04 2004 --- fs/udf/udf_vnops.c Tue Jan 11 03:12:38 2005 *************** static int udf_strategy(struct vop_strat *** 65,72 **** static int udf_bmap(struct vop_bmap_args *); static int udf_lookup(struct vop_cachedlookup_args *); static int udf_reclaim(struct vop_reclaim_args *); ! static int udf_readatoffset(struct udf_node *, int *, int, struct buf **, uint8_t **); ! static int udf_bmap_internal(struct udf_node *, uint32_t, daddr_t *, uint32_t *); vop_t **udf_vnodeop_p; static struct vnodeopv_entry_desc udf_vnodeop_entries[] = { --- 65,72 ---- static int udf_bmap(struct vop_bmap_args *); static int udf_lookup(struct vop_cachedlookup_args *); static int udf_reclaim(struct vop_reclaim_args *); ! static int udf_readatoffset(struct udf_node *, int *, off_t, struct buf **, uint8_t **); ! static int udf_bmap_internal(struct udf_node *, off_t, daddr_t *, uint32_t *); vop_t **udf_vnodeop_p; static struct vnodeopv_entry_desc udf_vnodeop_entries[] = { *************** udf_read(struct vop_read_args *a) *** 407,414 **** struct udf_node *node = VTON(vp); struct buf *bp; uint8_t *data; int error = 0; ! int size, fsize, offset; if (uio->uio_offset < 0) return (EINVAL); --- 407,415 ---- struct udf_node *node = VTON(vp); struct buf *bp; uint8_t *data; + off_t fsize, offset; int error = 0; ! int size; if (uio->uio_offset < 0) return (EINVAL); *************** udf_read(struct vop_read_args *a) *** 417,423 **** while (uio->uio_offset < fsize && uio->uio_resid > 0) { offset = uio->uio_offset; ! size = uio->uio_resid; error = udf_readatoffset(node, &size, offset, &bp, &data); if (error == 0) error = uiomove(data, size, uio); --- 418,424 ---- while (uio->uio_offset < fsize && uio->uio_resid > 0) { offset = uio->uio_offset; ! size = min (uio->uio_resid, fsize - uio->uio_offset); error = udf_readatoffset(node, &size, offset, &bp, &data); if (error == 0) error = uiomove(data, size, uio); *************** udf_reclaim(struct vop_reclaim_args *a) *** 1060,1066 **** * */ static int ! udf_readatoffset(struct udf_node *node, int *size, int offset, struct buf **bp, uint8_t **data) { struct udf_mnt *udfmp; struct file_entry *fentry = NULL; --- 1061,1067 ---- * */ static int ! udf_readatoffset(struct udf_node *node, int *size, off_t offset, struct buf **bp, uint8_t **data) { struct udf_mnt *udfmp; struct file_entry *fentry = NULL; *************** udf_readatoffset(struct udf_node *node, *** 1107,1113 **** * block. */ static int ! udf_bmap_internal(struct udf_node *node, uint32_t offset, daddr_t *sector, uint32_t *max_size) { struct udf_mnt *udfmp; struct file_entry *fentry; --- 1108,1114 ---- * block. */ static int ! udf_bmap_internal(struct udf_node *node, off_t offset, daddr_t *sector, uint32_t *max_size) { struct udf_mnt *udfmp; struct file_entry *fentry; ------------------------------------------------------------------------- | Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com | | John Wehle | Fax: 1-215-540-5495 | | ------------------------------------------------------------------------- From owner-freebsd-fs@FreeBSD.ORG Tue Jan 11 12:46:45 2005 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 B7E1816A4CE for ; Tue, 11 Jan 2005 12:46:45 +0000 (GMT) Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6313643D41 for ; Tue, 11 Jan 2005 12:46:45 +0000 (GMT) (envelope-from simon_freebsd_fs@bigblue.demon.co.uk) Received: from demon-gw.ledwoodtechnology.co.uk ([80.177.235.49] helo=[192.168.25.19]) by anchor-post-34.mail.demon.net with esmtp (Exim 4.42) id 1CoLQ4-000Oz4-Dt for freebsd-fs@freebsd.org; Tue, 11 Jan 2005 12:46:44 +0000 Message-ID: <41E3CAB4.5000009@bigblue.demon.co.uk> Date: Tue, 11 Jan 2005 12:46:44 +0000 From: Simon Truss User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en, en-us MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: nfs server busy lockup on 5.3 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, 11 Jan 2005 12:46:45 -0000 Hi, I've been experiencing a series of lockups of nfs recently which normally require a reboot to clear. Im about to submit a PR so any pointers on what I could check, trace or dump would be helpful. linux 2.6.8.1 nfs client copy or move of large files onto server causes nfsd to lock. Any access from client of the mount causes those processes to lock, and any access on the server to the directory containing the destination file causes a lockup of that program. I noted that systat -vmstat shows 25% disc usage and 75% cpu usage. The lockup usually occurs within a few 10's or 100's of MBs of the first file. note files are 2-5GB. A workaround and possible hint at the cause is to disable soft-deps, that at least has enabled me to run the system in a stable manner. The system has been stable for 2 weeks now with around 150+GB of data transfered without problem. system details: nfs client is linux, slackware 10.0, 2.6.8.1 kernel with rpc workqueue and rpc queue lock patches, http://client.linux-nfs.org/Linux-2.6.x/2.6.8.1/ (49 and 50 only) Server FreeBSD 5.3 GENERIC, problem also present with recent cvsup of 5.3. nfs exports are from a FFS1 file system on pst RAID array. I also note that this system was running without this problem with 5.1. The root partition is not on the pst array. Simon From owner-freebsd-fs@FreeBSD.ORG Thu Jan 13 09:05:05 2005 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 9161016A4CE; Thu, 13 Jan 2005 09:05:05 +0000 (GMT) Received: from as.itesm.mx (as.itesm.mx [200.34.200.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id C464443D31; Thu, 13 Jan 2005 09:05:04 +0000 (GMT) (envelope-from ccardena@itesm.mx) X-Ironport-AV: i="3.88,119,1102312800"; d="scan'208"; a="45508937:sNHT13680588" Received: from [137.194.164.215] by itesm.mx with HTTP; Thu, 13 Jan 2005 03:05:02 -0600 Date: Thu, 13 Jan 2005 10:05:02 +0100 Message-ID: <41E11BD300003B8D@mailserver3.itesm.mx> From: =?ISO-8859-15?Q?C=E9sar=20C=E1rdenas?= To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable cc: freebsd-fs@freebsd.org cc: freebsd-performance@freebsd.org cc: freebsd-i386@freebsd.org Subject: File System Full Error X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ccardena@itesm.mx List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 09:05:05 -0000 Dear all, Apologize if I am not posting on the correct forum, I am a very new FReeB= SD user...I'm using FreeBSD 4.5 Release P20 I have a problem concerning "file system full"... Results from "df" command are: ****************************** Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 99183 51233 40016 56% / /dev/ad0s1f 4379991 1317599 2711993 33% /usr /dev/ad0s1e 19815 19788 -1558 109% /var procfs 4 4 0 100% /proc ****************************** To my understanding memory device "ad0s1e" should be 50Mo for better perf= ormance...Which file I must change for correcting the problem marked in device "ad0s1e" and which command? I guess after changing such a file I must restart computer, is there any command for doing that because I am remotly accessing this machine? Thanks for any advice, have a nice day, C=E9sar C=E1rdenas (ccardena@itesm.mx) Electronics and Computer Science Department Monterrey Tech, Quer=E9taro Campus http://www.qro.itesm.mx Personal Phone: +(33) 625249469 Office Phone: +(33) 145817146 Office Fax: +(33) 145817158 All phones and fax from abroad France The content of this data transmission is not considered as an offer, prop= osal, understanding, or agreement unless it is confirmed in a document signed by a legal representative of ITESM. The content of this data transmission= is confidential and it is intended to be delivered only to the addresses,= therefore, it shall not be distributed and/or disclosed through any mean without the original sender's previous authorization. If you are not the addressee you are forbidden to use it, either totally or partially, for any purpose. From owner-freebsd-fs@FreeBSD.ORG Fri Jan 14 23:08:34 2005 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 8781016A4CE; Fri, 14 Jan 2005 23:08:34 +0000 (GMT) Received: from p548151A5.dip.t-dialin.net (p548151A5.dip.t-dialin.net [84.129.81.165]) by mx1.FreeBSD.org (Postfix) with SMTP id EC5CC43D3F; Fri, 14 Jan 2005 23:08:31 +0000 (GMT) (envelope-from ggnbhzetxfnr@gc.net) Received: from electrophoresis.worldpassage.net ([204.98.0.94]) (built Aug 20 2004)) with ESMTP id <0L6J00KE382UV85@fill.fresno.com> for freebsd-fs@freebsd.org (ORCPT freebsd-fs@freebsd.org); Fri, 14 Jan 2005 22:03:33 -0100 (IST) Received: from announce (contradistinct.worldpassage.net ([196.110.170.216]) DET17677 (AUTH gouge) ; Sat, 15 Jan 2005 03:08:33 +0400 (IST) Date: Sat, 15 Jan 2005 03:01:33 +0400 From: "Garry Maynard" To: References: In-Reply-To: Message-ID: <892565334172.KCY69497@piece.fresno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Subject: RE : pain specialist on thursday at 15-00 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, 14 Jan 2005 23:08:34 -0000 become the health man V-1_C^o.D'1,N 30/325 m*gg 30 PIllS 109.O0 6O P!|LS 189.99 90 P1||S 259.oo 18o P1llS 429.O0 create an 0.r.d.e.r : http://gradient.24-7medz.com/s/?acc5 Same Day Sh1pp1ng To En0ugh : http://officious.24-7medz.com/rms.html call me soon Patrick Ibarra Furrier Promega GmbH, D-68199 Manheim, Germany Phone: 147-961-9315 Mobile: 291-411-7191 Email: ggnbhzetxfnr@gc.net THIS IS AN AUTO-GENERATED MESSAGE - PLEASE DO NOT REPLY TO THIS MESSAGE This shareware is a 23 second usage software NOTES: The contents of this e-mail is for understanding and should not be ursuline cornmeal hagen al hoarse Time: Sat, 15 Jan 2005 01:08:33 +0200