Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, the urgency is appreciated, however - this has *nothing* to do with drbd. The space drbd is leaving usable is 61925464 1k blocks, of which you have used 54821544. drbd internals have nothing to do with this, and you would see the same shenanigans if this was a plain old disk. The most likely culprit are unlinked files that are still held open. I suggest taking a peek using `lsof | grep deleted`, there's probably a small number of large files filling your disk space. You will then likely want to restart a service or two. HTH, Felix On 02/07/2013 06:39 AM, Markus.Lutz at swisscom.com wrote: > Hello, > > We’ve recently noticed that one of our file system is runnig out of free space : > df -k > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/drbd1 61925464<tel:61925464> 54821544<tel:54821544> 3958292<tel:3958292> 94% /xxx > > Having a look with ‘du’ shows, that only 35GB are used. > When I mounted that file system on the secondary node, all values are okay: > /dev/drbd1 61925464<tel:61925464> 34424544<tel:34424544> 24355292<tel:24355292> 59% /xxx > > What ist he reason for the difference of 20GB? (Activity log or other meta data?) And what can I do now to get free space back? > > Output of /prod/drbd on primary node (the one with the size problem) : > version: 8.4.1 (api:1/proto:86-100) > GIT-hash: 91b4c048c1a0e06777b5f65d312b38d47abaea80 build by xyz at xxx, 2012-07-06 07:19:33 > 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate B r----- > ns:4448320<tel:4448320> nr:0 dw:767861356<tel:767861356>dr:952302182<tel:952302182> al:132509 bm:7766 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0 > > Output of /proc/drbd on secondary node : > 1: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate B r----- > ns:0 nr:23524 dw:178758696<tel:178758696>dr:566276537<tel:566276537> al:51 bm:487 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0 > > Kind regards, > > > Markus Lutz