Date: Mon, 29 Jul 2002 22:25:14 -0400 From: "David E. Cross" <crossd@cs.rpi.edu> To: Robert Watson <rwatson@freebsd.org> Cc: "David E. Cross" <crossd@cs.rpi.edu>, fs@freebsd.org, guptar@cs.rpi.edu, crossd@cs.rpi.edu Subject: Re: UFS Journaling Project Message-ID: <200207300225.g6U2PEO23038@monica.cs.rpi.edu> In-Reply-To: Message from Robert Watson <rwatson@freebsd.org> of "Mon, 29 Jul 2002 19:13:42 EDT." <Pine.NEB.3.96L.1020729190915.46084A-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1020729190915.46084A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> That's fairly odd. When I added extended attribute support to UFS, I > simply stuck the new structure (ufs_extattr_per_mount) in struct ufsmount > and never looked back. I can't, offhand, imagine what you're running into > -- ufsmount should only ever be in-memory, and never on disk. > > Not sure I really have any useful suggestions, other perhaps than to > experiment a bit and see what exactly triggers the problem. Try adding > long[] arrays at various points in the structure, and see what size and > location cause the problem to kick in. > > Very strange... Its funny you should mention extattr, that is exactly the example we have been following for this so far, and precisely the "grouping" of UFS extensions we were after. For now placing our addition at the tail end of ufsmount is working. We can track down the crud later. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207300225.g6U2PEO23038>