From owner-freebsd-fs@freebsd.org  Thu Dec 29 21:53:02 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64907C96DC5
 for <freebsd-fs@mailman.ysv.freebsd.org>; Thu, 29 Dec 2016 21:53:02 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from mail.in-addr.com (mail.in-addr.com
 [IPv6:2a01:4f8:191:61e8::2525:2525])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3135E12C0
 for <freebsd-fs@freebsd.org>; Thu, 29 Dec 2016 21:53:02 +0000 (UTC)
 (envelope-from gpalmer@freebsd.org)
Received: from gjp by mail.in-addr.com with local (Exim 4.87_1 (FreeBSD))
 (envelope-from <gpalmer@freebsd.org>)
 id 1cMid9-0000bT-C2; Thu, 29 Dec 2016 21:52:59 +0000
Date: Thu, 29 Dec 2016 21:52:59 +0000
From: Gary Palmer <gpalmer@freebsd.org>
To: "Julian H. Stacey" <jhs@berklix.com>
Cc: Kirk McKusick <mckusick@mckusick.com>, freebsd-fs@freebsd.org
Subject: Re: when ufs is 99% full, current seems to limit creat to 28672 bytes
Message-ID: <20161229215258.GA2169@in-addr.com>
References: <201612262313.uBQNDNrX030075@chez.mckusick.com>
 <201612292039.uBTKdGR4033963@fire.js.berklix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201612292039.uBTKdGR4033963@fire.js.berklix.net>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: gpalmer@freebsd.org
X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2016 21:53:02 -0000

On Thu, Dec 29, 2016 at 09:39:16PM +0100, Julian H. Stacey wrote:
> It was really a temporary cludge of mine to tickle for bad blocks,
> working from inside the file system. I'd better do it properly,
> unmount & experiment with eg camcontrol on the partition or whole
> disk, or search ports/ &/or write  a little C prog that reads blocks
> from a file (aka dev name of partition or whole disk, stores, to
> memory, & writes back blocks)

You may want to try recoverdisk(1).  I'm not sure, I've never used
it to read and write to the same device

Regards,

Gary