Date: Sat, 27 May 2006 00:50:59 +0400 From: Sergey Matveychuk <sem@FreeBSD.org> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-current@freebsd.org, Alex Dupre <ale@FreeBSD.org> Subject: Re: geli stops work Message-ID: <44776A33.6070200@FreeBSD.org> In-Reply-To: <20060526152120.GD1165@garage.freebsd.pl> References: <4475E51A.4090004@FreeBSD.org> <4475F779.1010704@FreeBSD.org> <44769644.6020505@FreeBSD.org> <20060526152120.GD1165@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44776A33.6070200>