From owner-freebsd-current@FreeBSD.ORG Fri May 26 20:51:24 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36D7A16AEB6; Fri, 26 May 2006 20:51:24 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC94C43D46; Fri, 26 May 2006 20:51:23 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from [87.240.16.199] (helo=[192.168.0.4]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1FjjHD-000A70-MW; Sat, 27 May 2006 00:51:19 +0400 Message-ID: <44776A33.6070200@FreeBSD.org> Date: Sat, 27 May 2006 00:50:59 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.2 (X11/20060429) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <4475E51A.4090004@FreeBSD.org> <4475F779.1010704@FreeBSD.org> <44769644.6020505@FreeBSD.org> <20060526152120.GD1165@garage.freebsd.pl> In-Reply-To: <20060526152120.GD1165@garage.freebsd.pl> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Alex Dupre Subject: Re: geli stops work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 20:51:26 -0000 Pawel Jakub Dawidek wrote: > On Fri, May 26, 2006 at 09:46:44AM +0400, Sergey Matveychuk wrote: > +> Alex Dupre wrote: > +> > Sergey Matveychuk wrote: > +> >> # mount /dev/md0c.eli /mnt1 > +> >> mount: /dev/md0c.eli: Operation not permitted > +> >> > +> >> What's up? > +> >> My geli disk unavailable now. > +> > > +> > Just to be sure, did you try to run fsck on it? Maybe it's only a badly > +> > corrupted fs. > +> > +> It was not corrupted before I've updated. > +> I mount/umount it by hands every time. > > Device itself isn't corrupted - you would get: > > mount: /dev/md0c.eli: Invalid argument > > in such case. Try to fsck it without modifing the device: > > # fsck_ffs -n /dev/md0c.eli > > and see what's wrong exactly. > For me it just looks like the device wasn't unmounted cleanly. > # fsck_ffs -n /dev/md0c.eli ** /dev/md0c.eli (NO WRITE) ** Last Mounted on /mnt1 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 3655 files, 125633 used, 126313 free (129 frags, 31546 blocks, 0.1% fragmentation) Looks good. But can't mount. -- Dixi. Sem.