From owner-freebsd-scsi@FreeBSD.ORG Sun Dec 28 12:29:23 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C7981065670 for ; Sun, 28 Dec 2008 12:29:23 +0000 (UTC) (envelope-from e.scholtz@argonsoft.de) Received: from coyote.quickmin.net (coyote.quickmin.net [217.14.112.24]) by mx1.freebsd.org (Postfix) with ESMTP id 1C73C8FC17 for ; Sun, 28 Dec 2008 12:29:22 +0000 (UTC) (envelope-from e.scholtz@argonsoft.de) Received: (qmail 44842 invoked from network); 28 Dec 2008 13:29:21 +0100 Received: by simscan 1.4.0 ppid: 44839, pid: 44840, t: 0.0130s scanners: clamav: 0.94.1/m:49/d:8609 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=argonsoft.de; b=YZ8gFl/PUBI8EEo2dPXudnbCWHKW2ZN2IyLX7dRSm9SiJZHXFAdpEpddTjg19yM0yiBcunlk8BwXKi/UegKCSz0NgbIpnZy8aRMaMdV7XGxWY4GJ3UAIgOIgkZ4t64zfz8Dze1z6ogk2eYUXJIEVG2MfdK2tQrHCld+yvzbuQA0= ; Received: from dialbs-213-023-239-142.static.arcor-ip.net (HELO erik-scholtzs-macbook-pro-15.local) (00000150@213.23.239.142) by coyote.quickmin.net with SMTP; 28 Dec 2008 13:29:21 +0100 Message-ID: <49577118.1080700@argonsoft.de> Date: Sun, 28 Dec 2008 13:29:12 +0100 From: "Erik Scholtz, ArgonSoft GmbH" User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Danny Braniss References: <4956B01B.3000509@argonsoft.de> <49575045.4090601@argonsoft.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-scsi@freebsd.org Subject: Re: Problem with disklabel and filesystem over iSCSI X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2008 12:29:23 -0000 ok, i started the system in single-user-mode and brought up the iSCSI connection. I tried to install the ufs first, after each step I synced. No change - problem remains the same (newfs is failing). Then I installed the ZFS again, also synced after each step, then unmounted the iSCSI device, synced again (always at least three times). Then rebooted the system (going to single-user-mode again) and the ZFS is corrupted again with the same message. I don't think the buffers are the problem. Erik ----- ArgonSoft GmbH | Im Ermlisgrund 3 | 76337 Waldbronn Tel: +49 7243 71520 | Fax: +49 7243 715222 | http://www.argonsoft.de Umsatzsteuer-Identnummer: DE205762306 | Handelsregister: HRB2372E Geschäftsführer: Erik Scholtz Danny Braniss wrote: > > ok, so the problem is on shutdown/reboot. Buffers don't seem to be > flushed. > To check if this is correct, try shutdown, then under single user > unmount the iscsi, sync, sync, reboot > > danny > >> Hi, >> >> I tested the default iSCSI_initiator shipped with 7.0, 7.1RC1 and >> 7.1RC2. Additionally i changed it with that version from >> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.1.tar.gz with each >> release. The effect is with all combinations the same: >> >> 7.0 native / 7.0 + iscsi-2.1 >> 7.1RC1 native / 7.1RC1 + iscsi-2.1 >> 7.2RC2 native / 7.2RC2 + iscsi-2.1 >> >> >> Additionally info + tests: >> -------------------------- >> 1) I also checked it for ufs in dangerously dedicated mode - also the >> same effect. >> >> 2) After the reboot, the iSCSI device is back on /dev/da0 as expected. >> >> 3) The SAN system is a Hardware-SAN (iStor / GigaStor), that works >> without any problems under Ubuntu, CenOS, MacOS X, Windows and RedHat >> (all tested the last days) >> >> 4) I could get ufs to work with the following (terribly wrong) partition >> map: >> >> 0 40 39 - 12 unused 0 >> 40 409600 409639 da0s1 165 FreeBSD 0 >> 409640 1928708016 1929117655 da0s2 165 FreeBSD 0 >> 1929117656 262184 1929379839 - 12 unused 0 >> >> With this partition map, newfs runs without any failure. The filesystem >> is heavily damaged and can be repaired with fsck. After repairing, the >> fs can be mounted and used as normal. But when running a fsck, thousands >> of errors must be corrected and the result is an empty disk again (when >> answering all with YES - I ran it with -y flag, since there are too many >> questions to be answered manually, even when copying only three big >> files).