From owner-freebsd-fs@FreeBSD.ORG Tue Feb 19 13:27:04 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2644B3DF for ; Tue, 19 Feb 2013 13:27:04 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id B1427D22 for ; Tue, 19 Feb 2013 13:27:03 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id hi18so4768574wib.3 for ; Tue, 19 Feb 2013 05:26:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=hDyDQ/BdgeQGgw+6VZTeqj9wcZVR7AXl4Ev8z6bZs0k=; b=S5+5Wvb/+0nCcLJ2bSaLY2PUdJyunvCBZeOayOOFvwcThs0rZr3FF3OSbsN0B9YL1r 5MZunOG/zucsYZk+yWIuiD9s94qSLVju17jxL9GYXuddlbiKSL9YdGK88oQhsF9yZfNs 865x13GsLAPKU+cGC2rKYZFqQ+pAnXH0TJ9l0NCfOqaxWpQ50PlTnseTG4CX63ER6jG2 X8zQpEdUaRY03D6C4+eHjNlWO6LBK2qGITa0lFvhASoC0W0PUIrR3zlV5sJqW/mWCICg UA5KNxCL1E6b9mK5JvDM41gMlPt/NfA3bjzQxDoNGLle56KbEN6i2vPjDztjeaGnfr0C Gm9w== X-Received: by 10.180.24.229 with SMTP id x5mr25538857wif.17.1361280416728; Tue, 19 Feb 2013 05:26:56 -0800 (PST) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id s8sm25560861wif.9.2013.02.19.05.26.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Feb 2013 05:26:55 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: zfs raid1 error resilvering and mount From: Fleuriot Damien In-Reply-To: Date: Tue, 19 Feb 2013 14:26:54 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <2FC474DC-1905-4BEC-BFA6-037054B5437B@my.gd> References: <5D97BF07-ECF4-45B2-91AC-3431A75ECDB3@my.gd> <0ED6EC22-9875-45FF-ADFC-BB23C2C94FC0@my.gd> <8506B305-D696-4213-BA59-929E4886B10C@my.gd> To: Konstantin Kuklin X-Mailer: Apple Mail (2.1499) X-Gm-Message-State: ALoCoQmH3wfsydfdmsoI8C1Mv5fS9ai4n0AAiicrlz5Fl2gZqrLKJV5Td7udGd8wVeh4Ej7GTITt Cc: freebsd-fs@freebsd.org, zfs-discuss@opensolaris.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 13:27:04 -0000 Well I can't see anything else to help you, except trying to replace = your failed vdev and resilver from there=E2=80=A6 On Feb 19, 2013, at 2:24 PM, Konstantin Kuklin = wrote: > zfs set canmount=3Doff zroot/var/crash >=20 > i can`t do this, because zfs list empty >=20 > 2013/2/19 Fleuriot Damien : >> The thing is, perhaps you have corrupted blocks that weren't caught = either by ZFS or your drives' firmware, preventing the pool's operation. >>=20 >> Seeing zroot/var/crash is the problem, could you try: >>=20 >> 1/ booting from a live CD or flash >> 2/ NOT start a resilver >> 3/ run the command: >> zfs set canmount=3Doff zroot/var/crash >>=20 >>=20 >> This should prevent /var/crash from trying to be mounted from the ZFS = pool. >>=20 >> Perhaps this'll allow you to get further through the boot process and = perhaps even start your ZFS pool correctly. >>=20 >>=20 >>=20 >> On Feb 19, 2013, at 12:52 PM, Konstantin Kuklin = wrote: >>=20 >>> you understand me right, but my problem not in dead device... raid1 >>> must work correctly with 1 device and command to replace or = something >>> else not work, just freeze >>> i have only 2 warning about crash fs zroot/var/crash and thats all >>> have any idea, how i can repair it without default zfs tools like = zfs, zpool? >>>=20 >>>=20 >>> 2013/2/19 Fleuriot Damien : >>>> If I understand you correctly, you have: >>>> - booted another system from flash >>>> - NOT replaced the failed device >>>> - under this booted system, resilvering takes place automatically >>>>=20 >>>>=20 >>>> While I cannot tell why ZFS tries to resilver without a new, proper = device, I think it will only work once you've replaced the failed = device. >>>>=20 >>>> Could you try replacing the failed drive ? >>>>=20 >>>>=20 >>>> On Feb 19, 2013, at 12:39 PM, Konstantin Kuklin = wrote: >>>>=20 >>>>> i did`t replace disk, after reboot system not started (zfs = installed >>>>> as default root system) and i boot from another system(from flash) = and >>>>> resilvering has auto start and show me warnings with freeze >>>>> progress(dead on checking zroot/var/crash ) >>>>> replacing dead disk healing var/crash with <0x0> adress? >>>>>=20 >>>>> 2013/2/18 Fleuriot Damien : >>>>>> Reassure me here, you've replaced your failed vdev before trying = to resilver right ? >>>>>>=20 >>>>>> Your zpool status suggests otherwise, so I only want to make sure = this is a status from before replacing your drive. >>>>>>=20 >>>>>>=20 >>>>>> On Feb 18, 2013, at 8:48 AM, Konstantin Kuklin = wrote: >>>>>>=20 >>>>>>> i can`t do it, because resilvering in progress(freeze on 0.1%) = and zfs >>>>>>> list empty >>>>>>>=20 >>>>>>> 2013/2/17 Fleuriot Damien : >>>>>>>> Hmmm, zfs destroy -f zroot/var/crash ? >>>>>>>>=20 >>>>>>>> Then you can try to zfs mount -a >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Removing pjd and mm from cc, if they want to read your message = they're old enough to check their ML subscription. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> On Feb 17, 2013, at 3:46 PM, Konstantin Kuklin = wrote: >>>>>>>>=20 >>>>>>>>> hi, i have raid1 on zfs with 2 device on pool >>>>>>>>> first device died and boot from second not working... >>>>>>>>>=20 >>>>>>>>> i try to get http://mfsbsd.vx.sk/ flash and load from it with = zpool import >>>>>>>>> http://puu.sh/2402E >>>>>>>>>=20 >>>>>>>>> when i load zfs.ko and opensolaris.ko i see this message: >>>>>>>>> Solaris: WARNING: Can't open objset for zroot/var/crash >>>>>>>>> Solaris: WARNING: Can't open objset for zroot/var/crash >>>>>>>>>=20 >>>>>>>>> zpool status: >>>>>>>>> http://puu.sh/2405f >>>>>>>>>=20 >>>>>>>>> resilvering freeze with: >>>>>>>>> zpool status -v >>>>>>>>> ............. >>>>>>>>> zroot/usr:<0x28ff> >>>>>>>>> zroot/usr:<0x29ff> >>>>>>>>> zroot/usr:<0x2aff> >>>>>>>>> zroot/var/crash:<0x0> >>>>>>>>> root@Flash:/root # >>>>>>>>>=20 >>>>>>>>> how i can delete or drop it fs zroot/var/crash (1m-10m size i = didn`t >>>>>>>>> remember) and mount other zfs points with my data >>>>>>>>> -- >>>>>>>>> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC >>>>>>>>> =D0=9A=D1=83=D0=BA=D0=BB=D0=B8=D0=BD =D0=9A=D0=BE=D0=BD=D1=81=D1= =82=D0=B0=D0=BD=D1=82=D0=B8=D0=BD. >>>>>>>>> _______________________________________________ >>>>>>>>> freebsd-fs@freebsd.org mailing list >>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>>>>>>>> To unsubscribe, send any mail to = "freebsd-fs-unsubscribe@freebsd.org" >>>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> -- >>>>>>> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC >>>>>>> =D0=9A=D1=83=D0=BA=D0=BB=D0=B8=D0=BD =D0=9A=D0=BE=D0=BD=D1=81=D1=82= =D0=B0=D0=BD=D1=82=D0=B8=D0=BD. >>>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC >>>>> =D0=9A=D1=83=D0=BA=D0=BB=D0=B8=D0=BD =D0=9A=D0=BE=D0=BD=D1=81=D1=82=D0= =B0=D0=BD=D1=82=D0=B8=D0=BD. >>>>=20 >>>=20 >>>=20 >>>=20 >>> -- >>> =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC >>> =D0=9A=D1=83=D0=BA=D0=BB=D0=B8=D0=BD =D0=9A=D0=BE=D0=BD=D1=81=D1=82=D0= =B0=D0=BD=D1=82=D0=B8=D0=BD. >>=20 >=20 >=20 >=20 > -- > =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC > =D0=9A=D1=83=D0=BA=D0=BB=D0=B8=D0=BD =D0=9A=D0=BE=D0=BD=D1=81=D1=82=D0=B0= =D0=BD=D1=82=D0=B8=D0=BD.