Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2005-10-17 14:28:06 +0000 \ Tom Gissel: > I have a drbd resource and am seeing unexpected behavior during failure that > I'm hoping someone can help with. In this particular resource I don't need > complete durability (i.e. it is OK for secondary to catch up when it comes back > online) and am thus using protocol A and have the DRBD device mounted over NFS. > Shortly after performing a simple failure, drbdadm down <resource>, on the > secondary I am unable to write to the filesystem on the primary because it is > now a "Read-only file system". Initially the writes continue on the primary as > expected but after a couple seconds I see the following error: > > node01:~ # touch /shared0/tom > touch: cannot touch `/shared0/tom': Read-only file system have a look into syslog. did you by any chance use internal meta data, but created the file system on the underlying block device, instead of on /dev/drbd ? do you use a buggy kernel (bio_clone)? -- : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client.