From owner-freebsd-fs@FreeBSD.ORG Wed May 30 07:29:40 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 998B0106566C for ; Wed, 30 May 2012 07:29:40 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 164138FC17 for ; Wed, 30 May 2012 07:29:39 +0000 (UTC) Received: by lbon10 with SMTP id n10so3726273lbo.13 for ; Wed, 30 May 2012 00:29:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:organization:references:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=WWVDZ/LozHiF0HWYrgpgbP1Ka08AU3Pn1qEqan5vYgY=; b=LA2Eqkg/ETAxvNkV5fHAJgsH196h6UyUbeLXLskhSOzwxQ3Ar2LNiuOPLEyFKYcmBB RO4nLlne79OXtQ42ShyR7yN++qyyODc+1Ax8CEm5ifMwiDOuEF+zTqXqzkZYVkFIpgR2 XuJa8gazu2TDs9Dn+LGTxDVXCBFoUocwMV0we5yallR/i1IRWRs4XxlnXC8ynVJ4t+YL WZYQBPhReOsbUfXqjsmmKZKJhzirrL3kvT/z05EBhjSJ72x8QDa2MEfHI9pMobfHmzP/ +f02X5q5orXXQwQ0TejnT36W1ia45OmeZcEqS1F5IySnb9INpJuQWHxocjwjoagG3mq9 1zpA== Received: by 10.112.101.97 with SMTP id ff1mr6299156lbb.69.1338362978775; Wed, 30 May 2012 00:29:38 -0700 (PDT) Received: from localhost ([188.230.122.226]) by mx.google.com with ESMTPS id p2sm11115438lbj.4.2012.05.30.00.29.36 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 May 2012 00:29:37 -0700 (PDT) From: Mikolaj Golub To: resdev80@gmail.com Organization: TOA Ukraine References: <1338295953.17714.12.camel@brainbug-nb.office.ctco.lv> Sender: Mikolaj Golub Date: Wed, 30 May 2012 10:29:34 +0300 In-Reply-To: <1338295953.17714.12.camel@brainbug-nb.office.ctco.lv> (Juris Krumins's message of "Tue, 29 May 2012 15:52:33 +0300") Message-ID: <86ehq2nn35.fsf@in138.ua3> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: Hastd activemap cache flush and "request failed: FLUSH.: Operation not supported by device" messages. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2012 07:29:40 -0000 On Tue, 29 May 2012 15:52:33 +0300 Juris Krumins wrote: JK> Hi everybody. JK> I've recently setup two FreeBSD nodes to use them as a storage. JK> So I'm using hast over "MegaRAID SAS 1078" and ZFS filesystem created on JK> HAST resource devices from /dev/hast/*. JK> Everything looks good, but when I execute iozone tests, I'm constantly JK> getting following messages in /var/log/message: JK> primary node: JK> May 29 15:44:15 rook hastd[2313]: [mfid2] (primary) Local request failed JK> (Operation not supported by device): FLUSH. JK> May 29 15:44:15 rook hastd[2311]: [mfid0] (primary) Local request failed JK> (Operation not supported by device): FLUSH. JK> May 29 15:44:15 rook hastd[2312]: [mfid1] (primary) Local request failed JK> (Operation not supported by device): FLUSH. JK> May 29 15:44:15 rook hastd[2312]: [mfid1] (primary) Remote request JK> failed (Operation not supported by device): FLUSH. JK> May 29 15:44:15 rook hastd[2313]: [mfid2] (primary) Remote request JK> failed (Operation not supported by device): FLUSH. JK> May 29 15:44:15 rook hastd[2311]: [mfid0] (primary) Remote request JK> failed (Operation not supported by device): FLUSH. JK> secondary node: JK> May 29 15:43:41 rook2 hastd[2458]: [mfid1] (secondary) Request failed: JK> FLUSH.: Operation not supported by device. JK> May 29 15:43:41 rook2 hastd[2457]: [mfid0] (secondary) Request failed: JK> FLUSH.: Operation not supported by device. JK> May 29 15:43:41 rook2 hastd[2462]: [mfid2] (secondary) Request failed: JK> FLUSH.: Operation not supported by device. JK> I'v also found following topic JK> http://lists.freebsd.org/pipermail/freebsd-fs/2012-January/013385.html. JK> I've updated src, rebuild world and kernel and rebooted. I've also added JK> metaflush "off" options to /etc/hast.conf configuration file. But still JK> getting previously mentioned messages. Note, there are two sources of BIO_FLUSH operations in HAST: 1) BIO_FLUSH operations generated by HAST on metadata (activemap) update, if enabled (not disabled) in config. 2) BIO_FLUSH operations sent by a HAST user (filesystem). If the underlying provider doesn't support BIO_FLUSH, in the first case a warning "The provider doesn't support flushing write cache. Disabling it." will be generated and there will be no more attempt to flush on activemap update. In the second case the error 'Request failed: FLUSH.: Operation not supported by device' will be observed (as in your case). Before r225832 it logged on every BIO_FLUSH coming. Since r225832 HAST will try only once and only one error in logs should be observed after hastd start. JK> Can somebody point me to the right direction how to configure hastd to JK> throw this warning only once. JK> I'm using: JK> FreeBSD primary. 9.0-STABLE FreeBSD 9.0-STABLE #0: Tue May 29 12:53:44 JK> EEST 2012 root@primary.:/usr/obj/usr/src/sys/GENERIC amd64 JK> FreeBSD secondary. 9.0-STABLE FreeBSD 9.0-STABLE #0: Tue May 29 12:53:44 JK> EEST 2012 root@secondary.:/usr/obj/usr/src/sys/GENERIC amd64 r225832 has been merged to 9-STABLE on 4 Jan 2012 as r229509 and you shouldn't observe 'FLUSH: Operation not supported by device' constantly repeating. If you do this is very strange and you should recheck your build. Please provide the output of ident /sbin/hastd command. JK> and hast.conf configuration from both machines: JK> I've decided to put metaflush option on every single level just to be JK> sure. No effect. No need in disabling metaflush in your case. It will disable automatically after the first attempt failed. -- Mikolaj Golub