From owner-freebsd-questions@FreeBSD.ORG  Tue Apr 26 08:00:40 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 99A84106566B
	for <freebsd-questions@freebsd.org>;
	Tue, 26 Apr 2011 08:00:40 +0000 (UTC)
	(envelope-from freebsd@edvax.de)
Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14])
	by mx1.freebsd.org (Postfix) with ESMTP id 5B3FF8FC1C
	for <freebsd-questions@freebsd.org>;
	Tue, 26 Apr 2011 08:00:40 +0000 (UTC)
Received: from r55.edvax.de (port-92-195-63-56.dynamic.qsc.de [92.195.63.56])
	by mx02.qsc.de (Postfix) with ESMTP id 75D4521996;
	Tue, 26 Apr 2011 10:00:39 +0200 (CEST)
Received: from r55.edvax.de (localhost [127.0.0.1])
	by r55.edvax.de (8.14.2/8.14.2) with SMTP id p3Q80cCY001655;
	Tue, 26 Apr 2011 10:00:39 +0200 (CEST)
	(envelope-from freebsd@edvax.de)
Date: Tue, 26 Apr 2011 10:00:38 +0200
From: Polytropon <freebsd@edvax.de>
To: Denis Fortin <fortin@acm.org>
Message-Id: <20110426100038.19df9d90.freebsd@edvax.de>
In-Reply-To: <84D40BB2-4BC9-4B6A-9388-5C57D5815B17@acm.org>
References: <84D40BB2-4BC9-4B6A-9388-5C57D5815B17@acm.org>
Organization: EDVAX
X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
Subject: Re: disk problem: suggestion on how to handle...
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Polytropon <freebsd@edvax.de>
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 08:00:40 -0000

On Tue, 26 Apr 2011 07:08:21 +0200, Denis Fortin <fortin@acm.org> wrote:
> 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=-574217714356717568, length=16384)]error = 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.

You should replace it on the long run. :-)



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

You can use the tool "badsect" (from the base system) to
mark a sector as bad, as inodes are "dynamically allocated"
and do not "hard-wiredly" correspond to actual disk locations
per se. A tool for clearing inode information is "clri" which
should be used on unmounted partitions whenever possible.

Files like /usr/src/sys/bio.h and /usr/src/sys/geom/geom_vfs.c
give some hints about what the numbers are refering to. Sadly
I'm not a system programmer, so I can't be more specific.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...