Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Fri, May 25, 2012 at 9:37 AM, Christian Völker <cvoelker at knebb.de> wrote: > Hi >>> Steps I did: >>> - fsck -f (ext3) >> >> fsck of your /dev/drbdX device, I hope? >> > > Yes, on the /dev/drbd0. Otherwise fsck would have thrown errors, right? Only if the filesystem had errors. :) You can always pretty much do anything with DRBD's backing device if DRBD isn't using it. >>> - reduced filesystem to 1,400G >>> - drbdadm -- --new-size=1450G resize >>> - lvreduce drbdvol -L 1500G >>> - fsck -f >> >> Again, did you run this on your /dev/drbdX and not on your backing device? >> > > Yes. Pretty sure about it. "Pretty sure" doesn't help that much. Check your shell history. >> Kernel logs? > > I will post them this evening. >> >>> I assume after the first lvreduce the primary was already on diskless but performed the fsck pn the secondarys disk (which was still on the larger old size) >> >> If you ran your fsck on your DRBD like you would be expected to, then >> that shouldn't be a problem. The DRBD device would already have the >> smaller size as per "drbdadm resize". > > Well, then what could be a reason for both being diskless? Logs will tell. That's why I asked for them. Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now