From owner-freebsd-questions@FreeBSD.ORG  Tue Apr 26 05:26:53 2011
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 AFA551065673
	for <freebsd-questions@freebsd.org>;
	Tue, 26 Apr 2011 05:26:53 +0000 (UTC) (envelope-from fortin@acm.org)
Received: from hub.zap.qc.ca (hub.zap.qc.ca [200.46.208.47])
	by mx1.freebsd.org (Postfix) with ESMTP id 8630A8FC19
	for <freebsd-questions@freebsd.org>;
	Tue, 26 Apr 2011 05:26:53 +0000 (UTC)
Received: from [192.168.1.19] (APuteaux-554-1-91-229.w92-154.abo.wanadoo.fr
	[92.154.66.229])
	by hub.zap.qc.ca (Postfix) with ESMTPSA id 5A146131436
	for <freebsd-questions@freebsd.org>;
	Tue, 26 Apr 2011 05:08:23 +0000 (UTC)
From: Denis Fortin <fortin@acm.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Apr 2011 07:08:21 +0200
Message-Id: <84D40BB2-4BC9-4B6A-9388-5C57D5815B17@acm.org>
To: freebsd-questions@freebsd.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: disk problem: suggestion on how to handle...
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2011 05:26:53 -0000

Good morning,

I have a small server with an SSD drive in it that is having some =
problems.

Notably, dmesg has been repeatedly reporting the following error =
message:

	g_vfs_done():ad0s1a[READ(offset=3D-574217714356717568, =
length=3D16384)]error =3D 5

I realize that the best course of action is to replace the disk and =
restore from a backup, but this isn't really an option immediately.

So, is there a way to "mark the inode bad" and then launch an fsck ?  =
How can I turn "offset=3D-574217714356717568" into a usable piece of =
information?

Any suggestion welcome.

Denis, fortin@acm.org=