So, I can't recall - is this normal or not? Here's the situation:
secondary node is down
primary node comes up
drbd is started and times out (inittimeout 10)
drbdsetup /dev/nb0 primary
fsck.ext3 /dev/nb0:
e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
fsck.ext3: Attempt to read block from filesystem resulted in short read
while trying to open /dev/nb0
Could this be a zero-length partition?
Huh?
A mount causes the kernel to oops, but keep running. I've attached the
kernel traceback.
I'm a little concerned by the first two lines of the traceback saying that
the blocksize is 1024 then 4096. What is going on here?
Why can't I fsck or mount /dev/nb0 that is the primary but is not connected?
Thanks,
Dan
--
Dan Yocum
Sloan Digital Sky Survey, Fermilab 630.840.6509
yocum@example.com, http://www.sdss.org
SDSS. Mapping the Universe.
secondary node is down
primary node comes up
drbd is started and times out (inittimeout 10)
drbdsetup /dev/nb0 primary
fsck.ext3 /dev/nb0:
e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
fsck.ext3: Attempt to read block from filesystem resulted in short read
while trying to open /dev/nb0
Could this be a zero-length partition?
Huh?
A mount causes the kernel to oops, but keep running. I've attached the
kernel traceback.
I'm a little concerned by the first two lines of the traceback saying that
the blocksize is 1024 then 4096. What is going on here?
Why can't I fsck or mount /dev/nb0 that is the primary but is not connected?
Thanks,
Dan
--
Dan Yocum
Sloan Digital Sky Survey, Fermilab 630.840.6509
yocum@example.com, http://www.sdss.org
SDSS. Mapping the Universe.