From owner-freebsd-scsi@FreeBSD.ORG Sun Dec 28 14:41:26 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 17669106564A for ; Sun, 28 Dec 2008 14:41:26 +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 89DD18FC17 for ; Sun, 28 Dec 2008 14:41:25 +0000 (UTC) (envelope-from e.scholtz@argonsoft.de) Received: (qmail 52560 invoked from network); 28 Dec 2008 15:41:24 +0100 Received: by simscan 1.4.0 ppid: 52557, pid: 52558, t: 0.0133s 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=kRJAy/1uKNM9QltidXbNLhiKqc8i/EBXtb0aYzKdkuDWlg207nucCmqDyWC5IeNoUtWKavJJ+YXN2+ifFaArOg5/qtlJ7Egv5ixs79wwGIFIfiUXV9kVJK6AB1FdaWKF9emHOLMWic5iaXf3fbQzgge43E/4Gtuif+srgwzq8Z8= ; 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 15:41:22 +0100 Message-ID: <4957900D.80601@argonsoft.de> Date: Sun, 28 Dec 2008 15:41:17 +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> <49577118.1080700@argonsoft.de> <4957824C.1000601@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 14:41:26 -0000 Well, I'm trying to find a solution to this problem - I already spend 6 whole days in testing, downloading and reading "FM"s, "HowTo"s and Mailinglists. I don't want to waste the time of others, so giving as lot information as possible and do the testing is the least I can do. I downgraded the SAN from 1Tb to 200GB: ------------------------------------------------------------ web3# fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=26108 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=26108 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 ------------------------------------------------------------ Partition: 0 63 62 - 12 unused 0 63 419424957 419425019 da0s1 8 freebsd 165 419425020 5380 419430399 - 12 unused 0 1) Result of newfs in compatible mode: 419256288 internal error: can't find block in cyl 0 2) Result of newfs in dangerously dedicated mode: ..., ..., ... 419256288 cg 0: bad magic number ZFS remains the same (all cases: before and after umounting the volume via "zfs umount" executing the "/etc/rc.d/zfs stop" - sync before and after zfs stop). When starting the zfs without rebooting, the FS is still ok. After reboot the FS is broken again. Again the fdisk output before the SAN was downgraded: >web3# fdisk /dev/da0s1 > ******* Working on device /dev/da0s1 ******* > parameters extracted from in-core disklabel are: > cylinders=3D99693 heads=3D255 sectors/track=3D63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=3D99693 heads=3D255 sectors/track=3D63 (16065 blks/cyl) 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: > Since you seem to be in a cooperative mood :-), can you try checking > with a smaller volume? say 200GB? either UFS or ZFS? > the biggest I have access to is 921595 Meg and it does not show your problems. > also, what is the Media Sector size? > fdisk da0 should show it. > > cheers, > danny > >