Well after a couple of weeks of beating my head, i finally got my data back so
I thought I would post what process recovered it.
I ran the samsung estool utility
ran auto-scan and for each disk that was showing the wrong physical size i :-
chose set max address
chose recover native size
After
On Sat, 13 Dec 2008, Brett wrote:
I will just say though that there is something in zfs which caused
this in the first place as when i first replaced teh faulty sata
controller, only 1 of the 4 disks showed the incorrect size in
format but then as i messed around trying to zpool
Well it shows that you're not suffering from a known bug. The symptoms
you were describing were the same as those seen when a device
spontaneously shrinks within a raid-z vdev. But it looks like the sizes
are the same (config asize = asize), so I'm at a loss.
- Eric
On Sun, Dec 07, 2008 at
here is the requested output of raidz_open2.d upon running a zpool status :-
[EMAIL PROTECTED]:/export/home/brett# ./raidz_open2.d
run 'zpool import' to generate trace
60027449049959 BEGIN RAIDZ OPEN
60027449049959 config asize = 4000755744768
60027449049959 config ashift = 9
60027507681841
As a result of a power spike during a thunder storm I lost a sata controller
card. This card supported my zfs pool called newsan which is a 4 x samsung 1Tb
sata2 disk raid-z. I replaced the card and the devices have the same
controller/disk numbers, but now have the following issue.
Can you send the output of the attached D script when running 'zpool
status'?
- Eric
On Thu, Dec 04, 2008 at 02:58:54PM -0800, Brett wrote:
As a result of a power spike during a thunder storm I lost a sata controller
card. This card supported my zfs pool called newsan which is a 4 x samsung
