From owner-freebsd-questions@FreeBSD.ORG Thu May 31 11:53:11 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 224EE106564A for ; Thu, 31 May 2012 11:53:11 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id D6C6F8FC08 for ; Thu, 31 May 2012 11:53:10 +0000 (UTC) Received: from r56.edvax.de (port-92-195-20-192.dynamic.qsc.de [92.195.20.192]) by mx01.qsc.de (Postfix) with ESMTP id C8A3F3D1E5; Thu, 31 May 2012 13:46:36 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id q4VBkaIN001927; Thu, 31 May 2012 13:46:36 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 31 May 2012 13:46:36 +0200 From: Polytropon To: dmitry@zhigulinet.ru Message-Id: <20120531134636.e070cef2.freebsd@edvax.de> In-Reply-To: <546749752.20120531141933@zhigulinet.ru> References: <546749752.20120531141933@zhigulinet.ru> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: fsck on a mounted fs as read-only X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 May 2012 11:53:11 -0000 On Thu, 31 May 2012 14:19:33 +0400, dmitry@zhigulinet.ru wrote: > Good afternoon. > Could not tell whether you can run fsck on checking mounted > file system as read-only, if prior to that with which the parameters > > > ftp # mount > ... > / dev/aacd0 on / var / ftp (ufs, NFS exported, local, read-only) > > Launched with these parameters and this is what gives > > ftp # fsck -yf / dev/aacd0 > ** / Dev/aacd0 (NO WRITE) > ** Last Mounted on / var / ftp > ** Phase 1 - Check Blocks and Sizes > > As I understand it does not fix the fsck filesystem. Correct. For file system modifications the file system may not be mounted because "lower level operations" maybe will take place. In your current setting, only checks will be performed, but _if_ something needs to be modified, it will not happen. The reason: It _might_ affect the file system to change, even if it's "just" in read-only state. Solution: Unmount the file system and re-run fsck. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...