Date: Sun, 28 Dec 2008 15:17:15 +0200 From: Danny Braniss <danny@cs.huji.ac.il> To: "Erik Scholtz, ArgonSoft GmbH" <e.scholtz@argonsoft.de> Cc: freebsd-scsi@freebsd.org Subject: Re: Problem with disklabel and filesystem over iSCSI Message-ID: <E1LGvW7-000ALB-Sl@kabab.cs.huji.ac.il> In-Reply-To: <49577118.1080700@argonsoft.de> References: <4956B01B.3000509@argonsoft.de> <E1LGrjK-0007Zn-5K@kabab.cs.huji.ac.il> <49575045.4090601@argonsoft.de> <E1LGti5-0009Dv-Uo@kabab.cs.huji.ac.il> <49577118.1080700@argonsoft.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> ok, i started the system in single-user-mode and brought up the iSCSI=20 > connection. I tried to install the ufs first, after each step I synced.= =20 > No change - problem remains the same (newfs is failing). >=20 > Then I installed the ZFS again, also synced after each step, then=20 > unmounted the iSCSI device, synced again (always at least three times).= =20 > Then rebooted the system (going to single-user-mode again) and the ZFS = > is corrupted again with the same message. >=20 in the case of zfs, you have to /etc/rc.d/zfs stop > I don't think the buffers are the problem. >=20 are you sure that the iscsi target is only used by the freebsd host? > Erik >=20 > ----- > ArgonSoft GmbH =7C Im Ermlisgrund 3 =7C 76337 Waldbronn > Tel: +49 7243 71520 =7C Fax: +49 7243 715222 =7C http://www.argonsoft.= de > Umsatzsteuer-Identnummer: DE205762306 =7C Handelsregister: HRB237= 2E > Gesch=E4ftsf=FChrer: Erik Scholtz >=20 > 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=20 > >> 7.1RC2. Additionally i changed it with that version from=20 > >> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.1.tar.gz with ea= ch=20 > >> 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 th= e=20 > >> same effect. > >> > >> 2) After the reboot, the iSCSI device is back on /dev/da0 as expecte= d. > >> > >> 3) The SAN system is a Hardware-SAN (iStor / GigaStor), that works=20 > >> without any problems under Ubuntu, CenOS, MacOS X, Windows and RedHa= t=20 > >> (all tested the last days) > >> > >> 4) I could get ufs to work with the following (terribly wrong) parti= tion=20 > >> 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 filesys= tem=20 > >> is heavily damaged and can be repaired with fsck. After repairing, t= he=20 > >> fs can be mounted and used as normal. But when running a fsck, thous= ands=20 > >> of errors must be corrected and the result is an empty disk again (w= hen=20 > >> answering all with YES - I ran it with -y flag, since there are too = many=20 > >> questions to be answered manually, even when copying only three big = > >> files).=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1LGvW7-000ALB-Sl>