> >> You're saying _any_ mount of ext4 over nbd does this sudden shutdown,
> >> with 3.2+ kernel? Surely that's not the case?
> >
> > Yes, it does unfortunately.
>
> Can you enable debug in the kernel module and tools and check the
> syslog for details? Does the nbd-server report anything in this case?
root@mdd-v2:~# time mkfs.ext4 -j /dev/nbd0
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1048576 inodes, 4194304 blocks
209715 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
128 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
real 0m16.361s
user 0m0.064s
sys 0m4.616s
(reverse-i-search)`': ^C
root@mdd-v2:~# mount /dev/nbd0 /mnt -o noatime
root@mdd-v2:~# cd /mnt
root@mdd-v2:/mnt# iozone -j 1024 -s 2g -r 128k -I -f test -+w 7
----------------------------------------------------------------------
3211: *NBD_CMD_WRITE from 8834316288 (17254524) len 22528, wr: net->buf,
*****************buf->exp, (WRITE to fd 6 offset 8834316288 len 22528 fua 0),
+OK!
3212: *NBD_CMD_WRITE from 1024 (2) len 1024, wr: net->buf, *buf->exp, (WRITE to
fd 6 offset 1024 len 1024 fua 0), +OK!
3213: *NBD_CMD_READ from 17179803648 (33554304) len 4096, exp->buf, +(READ from
fd 6 offset 17179803648 len 4096), buf->net, +OK!
3214: *NBD_CMD_READ from 17179860992 (33554416) len 4096, exp->buf, +(READ from
fd 6 offset 17179860992 len 4096), buf->net, +OK!
3215: *NBD_CMD_READ from 17179865088 (33554424) len 4096, exp->buf, +(READ from
fd 6 offset 17179865088 len 4096), buf->net, +OK!
3216: *NBD_CMD_READ from 17179734016 (33554168) len 4096, exp->buf, +(READ from
fd 6 offset 17179734016 len 4096), buf->net, +OK!
3217: *NBD_CMD_READ from 17179836416 (33554368) len 4096, exp->buf, +(READ from
fd 6 offset 17179836416 len 4096), buf->net, +OK!
3218: *NBD_CMD_READ from 17179738112 (33554176) len 4096, exp->buf, +(READ from
fd 6 offset 17179738112 len 4096), buf->net, +OK!
3219: *NBD_CMD_READ from 17179664384 (33554032) len 4096, exp->buf, +(READ from
fd 6 offset 17179664384 len 4096), buf->net, +OK!
3220: *NBD_CMD_READ from 0 (0) len 4096, exp->buf, +(READ from fd 6 offset 0
len 4096), buf->net, +OK!
3221: *NBD_CMD_READ from 4096 (8) len 4096, exp->buf, +(READ from fd 6 offset
4096 len 4096), buf->net, +OK!
3222: *NBD_CMD_READ from 4329472 (8456) len 4096, exp->buf, +(READ from fd 6
offset 4329472 len 4096), buf->net, +OK!
3223: *NBD_CMD_READ from 8724152320 (17039360) len 4096, exp->buf, +(READ from
fd 6 offset 8724152320 len 4096), buf->net, +OK!
3224: *NBD_CMD_WRITE from 0 (0) len 4096, wr: net->buf, **buf->exp, (WRITE to
fd 6 offset 0 len 4096 fua 0), +OK!
3225: *NBD_CMD_READ from 37883904 (73992) len 4096, exp->buf, +(READ from fd 6
offset 37883904 len 4096), buf->net, +OK!
3226: *Error: Read failed: Inappropriate ioctl for device
Exiting.
----------------------------------------------------------------------
root@mdd-v2:~# nbd-client -n 172.16.86.1 12342 /dev/nbd0
Negotiation: ..size = 16384MB
bs=1024, sz=17179869184 bytes
nbd,2857: Kernel call returned: 22Closing: que, sock, done
----------------------------------------------------------------------
...
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316732] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316736] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316739] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316746] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316773] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316777] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316780] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316784] nbd0: request ffff880014651c18:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316811] nbd0: request ffff880014651d90:
sending control (write@6448174080,130048B)
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316815] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316819] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316822] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316825] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316854] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316858] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316862] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316865] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316892] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316896] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316899] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316903] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316930] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316934] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316938] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316945] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316971] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316975] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316978] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.316982] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.317008] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.317012] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:37:16 mdd-v2 kernel: [ 78.317016] nbd0: request ffff880014651d90:
sending 1024 bytes data
Mar 25 21:38:16 mdd-v2 kernel: [ 139.109053] nbd0: request ffff88001efe1c98:
dequeued (flags=1)
Mar 25 21:38:16 mdd-v2 kernel: [ 139.109106] nbd0: request ffff88001efe1c98:
sending control (read@37883904,4096B)
Mar 25 21:38:16 mdd-v2 kernel: [ 139.109618] block nbd0: shutting down socket
Mar 25 21:38:16 mdd-v2 kernel: [ 139.109981] nbd0: request ffff88001efe1c98:
failed
Mar 25 21:38:16 mdd-v2 kernel: [ 139.109986] end_request: I/O error, dev nbd0,
sector 73992
Mar 25 21:38:16 mdd-v2 kernel: [ 139.110642] block nbd0: queue cleared
Mar 25 21:38:16 mdd-v2 kernel: [ 139.110864] nbd0: nbd_ioctl cmd=do-it(0xab03)
arg=140057575816704
Mar 25 21:38:16 mdd-v2 kernel: [ 139.111220] nbd0: nbd_ioctl
cmd=clear-que(0xab05) arg=140057575816720
Mar 25 21:38:16 mdd-v2 kernel: [ 139.111242] nbd0: nbd_ioctl
cmd=clear-sock(0xab04) arg=140057575816720
Mar 25 21:38:16 mdd-v2 kernel: [ 139.112725] nbd0: request ffff88001efe1e10:
dequeued (flags=1)
Mar 25 21:38:16 mdd-v2 kernel: [ 139.112736] block nbd0: Attempted send on
closed socket
Mar 25 21:38:16 mdd-v2 kernel: [ 139.113029] nbd0: request ffff88001efe1e10:
failed
Mar 25 21:38:16 mdd-v2 kernel: [ 139.113032] end_request: I/O error, dev nbd0,
sector 73992
Mar 25 21:38:17 mdd-v2 kernel: [ 140.113486] nbd0: request ffff88001f032250:
dequeued (flags=1)
Mar 25 21:38:17 mdd-v2 kernel: [ 140.113494] block nbd0: Attempted send on
closed socket
Folkert van Heusden
--
Always wondered what the latency of your webserver is? Or how much more
latency you get when you go through a proxy server/tor? The numbers
tell the tale and with HTTPing you know them!
http://www.vanheusden.com/httping/
-----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Nbd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nbd-general
