From owner-freebsd-fs@FreeBSD.ORG Thu Feb 1 13:18:59 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB13916A402 for ; Thu, 1 Feb 2007 13:18:59 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 68FD213C46B for ; Thu, 1 Feb 2007 13:18:59 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id E132F8441E; Thu, 1 Feb 2007 14:18:57 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 46447-04; Thu, 1 Feb 2007 14:18:52 +0100 (CET) Received: from [IPv6:::1] (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id D4C198441F; Thu, 1 Feb 2007 14:18:51 +0100 (CET) Message-ID: <45C1E8BB.2060907@fsn.hu> Date: Thu, 01 Feb 2007 14:18:51 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5.0.9 (X11/20070124) MIME-Version: 1.0 To: Kostik Belousov References: <45C1BFC9.7090104@fsn.hu> <20070201110321.GF56152@deviant.kiev.zoral.com.ua> In-Reply-To: <20070201110321.GF56152@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-fs@freebsd.org Subject: Re: g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2007 13:18:59 -0000 On 02/01/07 12:03, Kostik Belousov wrote: > On Thu, Feb 01, 2007 at 11:24:09AM +0100, Attila Nagy wrote: > >> Hello, >> >> I have a setup, where I have a /data filesystem with a "big" (20G) >> sparse file on it. This sparse file is set up with: >> mdconfig -a -t vnode -f /data/nfsimg >> and I use /dev/md0 for storing some data, shared via NFS (I needed >> redundant read only NFS servers, so I just sync this image to the others >> and mount read only on them). >> >> With the above, I get the following in the syslog: >> Feb 1 11:16:49 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 >> Feb 1 11:16:49 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1928118272, length=16384)]error = 1 >> Feb 1 11:17:18 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1350844416, length=16384)]error = 1 >> Feb 1 11:17:18 boot00a kernel: >> g_vfs_done():md0[WRITE(offset=1928118272, length=16384)]error = 1 >> >> And these two lines are alternating, with the same offsets, as you can >> see. I use the raw device for storing the filesystem (newfs /dev/md0). >> Currently the image is mounted read-write and there is almost no >> activity on that. >> >> Any ideas about this? >> > > errno == 1 == EPERM (Operation not permitted). Check for this. > Sorry, my fault. I forgot to tell that I use this image regurarly for reading/writing (to host OS environments for the boot clients) without any noticeable errors, except the above lines in the syslog. So it seems that the writes are OK, at least for the purpose of booting/running about 50 machines from this image with various OS-es (even Linux). -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/