[ENBD] New to ENBD, having troubles

Peter T. Breuer enbd@lists.community.tummy.com
Wed, 23 Jan 2002 03:00:59 +0100 (MET)


"A month of sundays ago Christopher Eveland wrote:"
> > I wonder if a strace of mke2fs would show it writing at sector -1, i.e.
> > at the 2TB range. Maybe somebody has decided to start getting ready for
> > terabyte sized devices.
> 
> beowulf1:/home/eveland/nbd-2.4.27# mke2fs -V
> mke2fs 1.25 (20-Sep-2001)
> 	Using EXT2FS Library version 1.25
> beowulf1:/home/eveland/nbd-2.4.27#
> 
> The output of the trace is below:
> 
> lseek(3, 8323072, SEEK_SET)             = 8323072

OK. About 8MB.

> write(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192)
> = 8192


> 1024) = 1024
> lseek(3, 2048, SEEK_SET)                = 2048
> write(3, "\3\0\0\0\4\0\0\0\5\0\0\0\356\36\365\7\2\0\0\0\0\0\0\0\0"..., 1024)
> = 1024
> fsync(3)                                = 0
> write(1, "done\n\n", 6)                 = 6
> write(1, "This filesystem will be automati"..., 133) = 133
> close(3)                                = 0
> _exit(0)                                = ?
> 
> 
> The fsync at the end seems to be where things get stuck.  When I do the
> "echo 0 > /proc/nbdinfo" it finishes up.  Hope this helps,

Not really.  I am able to reproduce this on 2.4.17.  It may be a kernel
issue.  Can you drop back to kernel 2.4.8 or 2.4.9 and see if the same
thing happens?  I'm busy patching 2.4.8 with ext3 in order to be able to
drop back right now ...

Peter