From owner-freebsd-questions@FreeBSD.ORG Wed May 6 19:07:10 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 617C21065677 for ; Wed, 6 May 2009 19:07:10 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 0BFC48FC0A for ; Wed, 6 May 2009 19:07:09 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id n46J6Kvk095505; Wed, 6 May 2009 15:06:20 -0400 (EDT) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id n46J6Jtx095504; Wed, 6 May 2009 15:06:19 -0400 (EDT) (envelope-from jerrymc) Date: Wed, 6 May 2009 15:06:19 -0400 From: Jerry McAllister To: Marc Coyles Message-ID: <20090506190619.GB95433@gizmo.acns.msu.edu> References: <00d301c9cd65$62298910$267c9b30$@wakefield.sch.uk> <44pren4cy5.fsf@be-well.ilk.org> <009401c9ce29$42b9bea0$c82d3be0$@wakefield.sch.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <009401c9ce29$42b9bea0$c82d3be0$@wakefield.sch.uk> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: Dump snapshot issue... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 19:07:10 -0000 On Wed, May 06, 2009 at 10:01:36AM +0100, Marc Coyles wrote: > > One thing you should try is to remove the dump_snapshot files, > > because > > they are supposed to be unlinked when the dump starts anyway, so > > they > > shouldn't be sticking around. > > > > Also, look for file flags on the directories, or ACLs, etc. > > > > And consider the permissions you're running dump with. > > > > Dump is running as root via cron / initiated by hand. > ACLs not used. > Have removed all existing dump_snapshot files, and > have also removed and recreated all .snap directories. > > S'now working fine for all mountpoints, except /home... > Is /home really a separate file system on your system? Or is it just a directory in another filesystem? ////jerry > mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error > dump: Cannot create /home/.snap/dump_snapshot: No such file or directory > > It doesn't appear to proceed "as normal" either... as you can see below, > it ends the previous dump, starts the /home dump, gets an I/O error, > then proceeds straight to the /usr dump. The /home dump never gets > performed. If I remove the -L option, everything goes thru fine, but > complains about lack of -L flag... > > DUMP: DUMP IS DONE > mksnap_ffs: Cannot create /home/.snap/dump_snapshot: Input/output error > dump: Cannot create /home/.snap/dump_snapshot: No such file or directory > > DUMP: Date of this level 0 dump: Wed May 6 08:30:31 2009 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping snapshot of /dev/da0s1e (/usr) to standard output > > > Fsck finds no errors on /home... point to note... mksnap_ffs CAN create > /home/.snap/dump_snapshot as I'm sat looking at the file, however, once > it's created it it's as tho it can't access it. The file is there, it > wasn't before I ran the script. It's created it as root:operator, perms > 400. I can open it in pico, add content to it, and save it happily. So > I'm baffled! > > M > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"