Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Still a little fuzzy about where my data can go in relation to drbd. My lower level is: /dev/sda2 /data my drbd device is: /dev/drbd1 The docs say not to access the lower level device after drbd is running so where do I put my files and data? If it's actually on the drbd1 device how to I access that? I cannot mount it like a partition using mount. My config still looks like: global { usage-count yes; } common { protocol C; } resource r0 { on clst01.example.net { device /dev/drbd1; disk /dev/sda2; address 10.233.2.71:7789; meta-disk /dev/sda6[0]; } on clst02.example.net { device /dev/drbd1; disk /dev/sda2; address 10.233.2.72:7789; meta-disk /dev/sda6[0]; } } Thanks Cameron On Wed, Mar 17, 2010 at 2:40 PM, Cameron Smith <velvetpixel at gmail.com>wrote: > Excellent! > Thanks for the clarification :) > > > On Wed, Mar 17, 2010 at 1:50 PM, Peter den Hartog < > peterdenhartog at gmail.com> wrote: > >> What David said.. What file system are you using? ext3? then you will only >> see the changes if the primary actually fails on the first machine. >> >> and oh you might want to higher up your sync rate, if you don't want to >> wait for 4 days for DRBD to finish the first sync :-D. >> >> >> >> On Wed, Mar 17, 2010 at 4:40 PM, Cameron Smith <velvetpixel at gmail.com>wrote: >> >>> I am stuck. >>> >>> I did in an initial install of DRBD and was able to achieve a sync from >>> primary to secondary! >>> >>> Maybe. >>> >>> My partition that is source on primary and destination on secondary is: >>> >>> /dev/sda2 /data >>> >>> When I create files in the /data directory I can see that DRBD is >>> recognizing that things are changing and when I run: >>> >>> cat /proc/drbd >>> >>> on both primary and secondary I see they both change if I modify or add >>> files in /data on the primary. >>> >>> >>> My question is why do I not see those same files on /data on the >>> secondary? >>> >>> Shouldn't they be there? >>> >>> >>> Here is the output of cat /proc/drbd from both systems: >>> >>> [[root at clst01 ~]# cat /proc/drbd >>> version: 8.0.16 (api:86/proto:86) >>> GIT-hash: d30881451c988619e243d6294a899139eed1183d build by >>> mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57 >>> >>> 1: cs:SyncSource st:Primary/Secondary ds:UpToDate/Inconsistent C r--- >>> ns:712320 nr:0 dw:0 dr:712320 al:0 bm:43 lo:0 pe:0 ua:0 ap:0 >>> [>....................] sync'ed: 1.2% (62300/62996)M >>> finish: 44:18:11 speed: 376 (320) K/sec >>> resync: used:0/61 hits:44476 misses:44 starving:0 dirty:0 changed:44 >>> act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0 >>> >>> >>> >>> [root at clst02 ~]# cat /proc/drbd >>> version: 8.0.16 (api:86/proto:86) >>> GIT-hash: d30881451c988619e243d6294a899139eed1183d build by >>> mockbuild at v20z-x86-64.home.local, 2009-08-22 13:26:57 >>> >>> 1: cs:SyncTarget st:Secondary/Primary ds:Inconsistent/UpToDate C r--- >>> ns:0 nr:718400 dw:718400 dr:0 al:0 bm:43 lo:0 pe:0 ua:0 ap:0 >>> [>....................] sync'ed: 1.2% (62292/62996)M >>> finish: 33:13:27 speed: 416 (320) K/sec >>> resync: used:0/61 hits:44856 misses:44 starving:0 dirty:0 changed:44 >>> act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0 >>> >>> >>> Thanks! >>> Cameron >>> >>> >>> >>> >>> _______________________________________________ >>> drbd-user mailing list >>> drbd-user at lists.linbit.com >>> http://lists.linbit.com/mailman/listinfo/drbd-user >>> >>> >> >> >> -- >> Groet // Kind regards, >> Peter den Hartog >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100317/f3e81845/attachment.htm>