headers
Piotr Paczynski | 1 Apr 2011 02:36
Picon

Re: ZFS failed after hard power off

> v28 was committed to -current on Feb 27th, so your snapshot is too
> old. You should be able to fix the pool with OpenIndiana liveDVD or
> liveUSB
> http://openindiana.org/download/

OK, after fiddling for like 4 hours I managed to run OpenIndiana
LiveDVD (wouldnt boot up which eventually turned out to by my KVM
fault) and then get it to see my 3ware 9650 arrays (needed to install
drivers from 3ware). The problem is my corrupted pool is not visible
by zpool command. Now, I have two pools on the server: zroot and
backup. The backup is visible (and not faulted) but zroot is not
visible under Solaris - this is the one I have problems with, and also
use as boot disk in FreeBSD:

root <at> openindiana:~# zpool import
  pool: backup
    id: 8416389847782759507
 state: ONLINE
status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier, though
	some features will not be available without an explicit 'zpool upgrade'.
config:

	backup        ONLINE
	  mirror-0    ONLINE
	    c4t1d0p0  ONLINE
	    c4t2d0s2  ONLINE
root <at> openindiana:~# zpool import zroot
cannot import 'zroot': no such pool available
root <at> openindiana:~# zpool import -fFn zroot
(Continue reading)

Permalink | Reply | 13 comments |
headers
Jeremy Chadwick | 1 Apr 2011 03:36

Re: ZFS failed after hard power off

On Fri, Apr 01, 2011 at 12:36:47AM +0000, Piotr Paczynski wrote:
> > v28 was committed to -current on Feb 27th, so your snapshot is too
> > old. You should be able to fix the pool with OpenIndiana liveDVD or
> > liveUSB
> > http://openindiana.org/download/
> 
> OK, after fiddling for like 4 hours I managed to run OpenIndiana
> LiveDVD (wouldnt boot up which eventually turned out to by my KVM
> fault) and then get it to see my 3ware 9650 arrays (needed to install
> drivers from 3ware). The problem is my corrupted pool is not visible
> by zpool command. Now, I have two pools on the server: zroot and
> backup. The backup is visible (and not faulted) but zroot is not
> visible under Solaris - this is the one I have problems with, and also
> use as boot disk in FreeBSD:
> 
> root <at> openindiana:~# zpool import
>   pool: backup
>     id: 8416389847782759507
>  state: ONLINE
> status: The pool is formatted using an older on-disk version.
> action: The pool can be imported using its name or numeric identifier, though
> 	some features will not be available without an explicit 'zpool upgrade'.
> config:
> 
> 	backup        ONLINE
> 	  mirror-0    ONLINE
> 	    c4t1d0p0  ONLINE
> 	    c4t2d0s2  ONLINE
> root <at> openindiana:~# zpool import zroot
> cannot import 'zroot': no such pool available
(Continue reading)

Permalink | Reply | 12 comments |
headers
Šimun Mikecin | 1 Apr 2011 09:53
Picon

Re: ZFS failed after hard power off


On 1. tra. 2011., at 03:36, Jeremy Chadwick wrote:

> On Fri, Apr 01, 2011 at 12:36:47AM +0000, Piotr Paczynski wrote:
>>> v28 was committed to -current on Feb 27th, so your snapshot is too
>>> old. You should be able to fix the pool with OpenIndiana liveDVD or
>>> liveUSB
>>> http://openindiana.org/download/
>> 
>> OK, after fiddling for like 4 hours I managed to run OpenIndiana
>> LiveDVD (wouldnt boot up which eventually turned out to by my KVM
>> fault) and then get it to see my 3ware 9650 arrays (needed to install
>> drivers from 3ware). The problem is my corrupted pool is not visible
>> by zpool command. Now, I have two pools on the server: zroot and
>> backup. The backup is visible (and not faulted) but zroot is not
>> visible under Solaris - this is the one I have problems with, and also
>> use as boot disk in FreeBSD:
>> 
>> root <at> openindiana:~# zpool import
>> pool: backup
>>   id: 8416389847782759507
>> state: ONLINE
>> status: The pool is formatted using an older on-disk version.
>> action: The pool can be imported using its name or numeric identifier, though
>> 	some features will not be available without an explicit 'zpool upgrade'.
>> config:
>> 
>> 	backup        ONLINE
>> 	  mirror-0    ONLINE
>> 	    c4t1d0p0  ONLINE
(Continue reading)

Permalink | Reply | 11 comments |
headers
Piotr Paczynski | 1 Apr 2011 12:34
Picon

Re: ZFS failed after hard power off

>> I believe the command here is wrong, and that you should be using "zpool
>> import 8416389847782759507" or "zpool import 8416389847782759507 zroot".
>> I've seen many cases where using the pool name doesn't work.

I can import the "backup" pool just fine using either its name or the
guid. The zroot pool is the problem.

> He has two pools: backup and zroot. Only backup is visible.
> So he shouldn't do as you suggested, because it will rename his backup pool to zroot, which will bring the
confusion, because it is not the original zroot pool.
> To be able to import his original zroot pool, it needs to be visible to "zpool import" as a first step.

Any idea how to make it visible to "zpool import"?

I've tried importing the zroot pool using its various guids, as show
by "zdb -l /dev/dsk/c3t0d0s2":

    version: 14
    name: 'zroot'
    pool_guid: 2082617533358360017
    top_guid: 1617266672942229358

but still no luck:

root <at> openindiana:~# zpool import 2082617533358360017
cannot import '2082617533358360017': no such pool available
root <at> openindiana:~# zpool import 1617266672942229358
cannot import '1617266672942229358': no such pool available
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
(Continue reading)

Permalink | Reply | 10 comments |
headers
Pete French | 1 Apr 2011 12:40
Picon

Re: Any success stories for HAST + ZFS?

> Yes, you may hit it only on hast devices creation. The workaround is to avoid
> using 'hastctl role primary all', start providers one by one instead.

Interesting to note that I just hit a lockup in hast (the discs froze
up - could not run hastctl or zpool import, and could not kill
them). I have two hast devices instead of one, but I am starting them
individually instead of  using 'all'. The copde includes all the latest
patches which have gone into STABLE over the last few days, none of which
look particularly controversial!

I havent tried your atch yet, nor been able to reporduce the lockup, but
thought you might be interested to know that I also had problems with
multiple providers.

cheers,

-pete.
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |
headers
Pete French | 1 Apr 2011 13:22
Picon

Re: Any success stories for HAST + ZFS?

> The other 5% of the time, the hastd crashes occurred either when
> importing the ZFS pool, or when running multiple parallel rsyncs to
> the pool.  hastd was always shown as the last running process in the
> backtrace onscreen.

This is what I am seeing - did you manage to reproduce this with the patch,
or does it fix the issue for you ? Am doing more test now, with only a single
hast device to see if it is stable. Am Ok to run without mirroring across
hast devices for now, but wouldnt like to do so long term!

-pete.
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Mikolaj Golub | 1 Apr 2011 14:31
Picon
Favicon

Re: Any success stories for HAST + ZFS?


On Fri, 01 Apr 2011 11:40:11 +0100 Pete French wrote:

 >> Yes, you may hit it only on hast devices creation. The workaround is to avoid
 >> using 'hastctl role primary all', start providers one by one instead.

 PF> Interesting to note that I just hit a lockup in hast (the discs froze
 PF> up - could not run hastctl or zpool import, and could not kill
 PF> them). I have two hast devices instead of one, but I am starting them
 PF> individually instead of  using 'all'. The copde includes all the latest
 PF> patches which have gone into STABLE over the last few days, none of which
 PF> look particularly controversial!

 PF> I havent tried your atch yet, nor been able to reporduce the lockup, but
 PF> thought you might be interested to know that I also had problems with
 PF> multiple providers.

This looks like a different problem. If you have this again please provide the
output of 'procstat -kka'.

--

-- 
Mikolaj Golub
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Pete French | 1 Apr 2011 14:32
Picon

Re: Any success stories for HAST + ZFS?

> This looks like a different problem. If you have this again please provide the
> output of 'procstat -kka'.

Will do...

-pete.
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Nicholas Radonicich | 1 Apr 2011 14:43
Favicon

Unable to remove ZIL from ZFS v28

Hello, I tried to remove the log device I was using testing ZFS, when I
ran zpool remove tank ad10 the system became unresponsive. I left it
overnight and no change thinking that the system was working things out.
Below is my zpool info, both the cache and log drives are basic SATA
discs. On reboot of the system I was unable to get past loading ZFS
without booting into singleuser and putting the log device offline. Once
offline (and unmounted) if I try to remove the log device the system
still hangs. I'm currently scrubbing the system but any help on getting
the device removed would be appreciated... or if more information is
needed that is no problem either.

FreeBSD less.cogeco.net 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Thu Mar 24
08:26:39 UTC 2011     nick <at> :/usr/obj/usr/src/sys/GENERIC  amd64

	NAME        STATE     READ WRITE CKSUM
	tank        DEGRADED     0     0     0
	  aacd0     ONLINE       0     0     0
	  aacd1     ONLINE       0     0     0
	  aacd2     ONLINE       0     0     0
	  aacd3     ONLINE       0     0     0
	logs
	  ad10      OFFLINE      0     0     0
	cache
	  ad6s2     ONLINE       0     0     0

errors: No known data errors 

Do you really need to print this email? Help preserve our environment! Devez-vous vraiment imprimer ce
courriel? Pensons a l'environnement!
__________________________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pawel Jakub Dawidek | 2 Apr 2011 08:33
Picon
Favicon

Re: fail to boot with zfs on root

On Thu, Mar 31, 2011 at 01:09:38PM -0700, Sife Mailling wrote:
> Recently I installed FreeBSD 8.2 AMD64 with zfs on root, the boot stop in this strange message:
> can't exec getty '/usr/libexec/getty' for port /dev/ttyv* no such file or directoryI tried to set
setuid=on on /usr but it doesn't help.

Do you have /dev/ttyv<X> entries? Do you have 'device sc' in you kernel
config? Is /usr/ file system mounted at that time and the
/usr/lobexec/getty file exists?

--

-- 
Pawel Jakub Dawidek                       http://www.wheelsystems.com
FreeBSD committer                         http://www.FreeBSD.org
Am I Evil? Yes, I Am!                     http://yomoli.com
Permalink | Reply | 0 comments |

Gmane