Am 10.01.14 17:16, schrieb Garrett D'Amore:
This looks like it probably is an error that should never happen.
Note that I can't see how this error could occur with existing
illumos, assuming that the disk targets are managed by "sd". (I am
thinking the assertion from ZFS is indicating a non-zero return from
strategy(), which should not be possible under any circumstance.)
I've not checked Joyent's tree, but I'd *really* like to know if this
is reproducible under stock illumos. (The backtrace you showed have
line addresses that don't make sense for illumos-gate, so this is
conjecture on my part.)
On the disk pool consisting of disks connected by dual-path SAS there
are ZVOLs, exported as COMSTAR LUNs via fibre channel (emlxs in target
mode).
These LUN's are imported via fcp as devices (emlxs in initiator mode),
and a zpool mirror is build from one from the local exportet target, one
from the remote system.
So there are two layers of ZFS in the system. All disk devices (SAS or
FC) should be presented by sd.
I will try switching off the shelf on another upcoming system in the
next week (which unfortunately has now FC in it),
as the current system is in friendly customer phase right now.
For tests on stock illumos directly, which distribution should I use ?
OmniOS (stable/bloody) or anything else ?
Thx,
Franz
zpool list -v
norddisk 97,9T 2,85T 95,0T - 2%
1.00x ONLINE -
raidz2 10,9T 325G 10,6T -
c0t5000C500575082EFd0 - - - -
c0t5000C50057690CFFd0 - - - -
c0t5000C500574FA357d0 - - - -
c0t5000C5005745196Fd0 - - - -
c0t5000C5005750511Fd0 - - - -
c0t5000C50057508AF7d0 - - - -
raidz2 10,9T 324G 10,6T -
c0t5000C50057500113d0 - - - -
c0t5000C500574FD207d0 - - - -
c0t5000C50057502437d0 - - - -
c0t5000C500576AD97Bd0 - - - -
c0t5000C500576B062Bd0 - - - -
c0t5000C500576AF7A3d0 - - - -
raidz2 10,9T 324G 10,6T -
c0t5000C50057507E87d0 - - - -
c0t5000C500574FFE7Fd0 - - - -
c0t5000C500576B0967d0 - - - -
c0t5000C5005743D637d0 - - - -
c0t5000C500575075D3d0 - - - -
c0t5000C5005750259Bd0 - - - -
raidz2 10,9T 324G 10,6T -
c0t5000C50057505FBBd0 - - - -
c0t5000C500576B06B3d0 - - - -
c0t5000C500576ADB2Bd0 - - - -
c0t5000C50057508F8Bd0 - - - -
c0t5000C5005750752Fd0 - - - -
c0t5000C500576B049Bd0 - - - -
raidz2 10,9T 325G 10,6T -
c0t5000C500576AFFE3d0 - - - -
c0t5000C5005743CD8Fd0 - - - -
c0t5000C500574FFA8Fd0 - - - -
c0t5000C50057435CCBd0 - - - -
c0t5000C500576AF25Fd0 - - - -
c0t5000C50057435867d0 - - - -
raidz2 10,9T 324G 10,6T -
c0t5000C50057504723d0 - - - -
c0t5000C50057412A77d0 - - - -
c0t5000C500576B0733d0 - - - -
c0t5000C5005750398Fd0 - - - -
c0t5000C500574FCC2Bd0 - - - -
c0t5000C500576B044Fd0 - - - -
raidz2 10,9T 323G 10,6T -
c0t5000C500575070B3d0 - - - -
c0t5000C500576B0BC3d0 - - - -
c0t5000C50057500043d0 - - - -
c0t5000C500575051F7d0 - - - -
c0t5000C500576B0357d0 - - - -
c0t5000C5005742392Bd0 - - - -
raidz2 10,9T 325G 10,6T -
c0t5000C500574643C7d0 - - - -
c0t5000C50057225793d0 - - - -
c0t5000C50057423ED3d0 - - - -
c0t5000C50057504D6Fd0 - - - -
c0t5000C50057463553d0 - - - -
c0t5000C50057689927d0 - - - -
raidz2 10,9T 324G 10,6T -
c0t5000C50057503963d0 - - - -
c0t5000C500576B04C3d0 - - - -
c0t5000C500576B010Bd0 - - - -
c0t5000C500574FBF1Bd0 - - - -
c0t5000C50057464923d0 - - - -
c0t5000C500576B0F6Bd0 - - - -
mirror 7,44G 9,39M 7,43G -
c0t5000A72030089FCAd0 - - - -
c0t5000A7203008BDFEd0 - - - -
nordp 31,2T 110G 31,1T - 0%
1.00x ONLINE -
mirror 31,2T 110G 31,1T -
c0t600144F09082C029000052CC68420010d0 - - - -
c0t600144F09082C021000052CC68740004d0 - - - -
stmfadm list-lu -v
LU Name: 600144F09082C029000052CC68420010
Operational Status: Online
Provider Name : sbd
Alias : /dev/zvol/rdsk/norddisk/nord1_nordp_vol1
View Entry Count : 1
Data File : /dev/zvol/rdsk/norddisk/nord1_nordp_vol1
Meta File : not set
Size : 34634616274944
Block Size : 512
Management URL : not set
Vendor ID : SUN
Product ID : COMSTAR
Serial Num : not set
Write Protect : Disabled
Writeback Cache : Enabled
Access State : Active
LU Name: 600144F09082C029000052CC75B60011
Operational Status: Online
Provider Name : sbd
Alias : /dev/zvol/rdsk/norddisk/nord1_suedp_vol1
View Entry Count : 1
Data File : /dev/zvol/rdsk/norddisk/nord1_suedp_vol1
Meta File : not set
Size : 34634616274944
Block Size : 512
Management URL : not set
Vendor ID : SUN
Product ID : COMSTAR
Serial Num : not set
Write Protect : Disabled
Writeback Cache : Enabled
Access State : Active
The ldi_strategy function in illumos-joyent driver_lyr.c looks just the
same to me as in joyent-gate:
ldi_strategy(ldi_handle_t lh, struct buf *bp)
{
struct ldi_handle *handlep = (struct ldi_handle *)lh;
dev_t dev;
if ((lh == NULL) || (bp == NULL))
return (EINVAL);
/* this entry point is only supported for cb devices */
dev = handlep->lh_vp->v_rdev;
if (!(handlep->lh_type & LH_CBDEV))
return (ENOTSUP);
bp->b_edev = dev;
bp->b_dev = cmpdev(dev);
return (bdev_strategy(bp));
}
Thx.
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
