From owner-freebsd-current Sun Apr 12 18:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05478 for freebsd-current-outgoing; Sun, 12 Apr 1998 18:50:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA05428 for ; Sun, 12 Apr 1998 18:50:41 -0700 (PDT) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA22044; Mon, 13 Apr 98 03:53:23 +0200 Date: Mon, 13 Apr 98 03:53:23 +0200 Message-Id: <9804130153.AA22044@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: freebsd-current@FreeBSD.ORG Subject: nightmare: dump/restore broken X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wanted to reorganize 2 disks: so I did a dump of the filesystems, relabeled/newfs'd the disks and restored the filesystems. This worked for the system disk (/, /usr, ....), but the situation is dramatic with my /home fs (the most important one, of course). After restore, I discovered that thousands (yes thousands :-() of files are empty and that a lot of other are truncated. It is also possible that some other files have grown. In short I losed 500Mbytes. I tried an old tape (2 months old): same result. I don't understand why the system files are ok, and this particular fs is broken. /dev/sd0a on / (NFS exported, local, writes: sync 153 async 1338)) /dev/sd0f on /usr (NFS exported, local, writes: sync 29 async 579)) /dev/sd0e on /var (local, writes: sync 179 async 479)) /dev/sd1e on /home (local, writes: sync 59 async 230)) I am runing a kernel from march, 30. Any help will be greatly appreciated... Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message