[DRBD-user] read-only access on Secondary for MySQL (InnoDB) Raw Partition?

[Josh McAllister]

I'm really not trying to be a pain in butt... just encouraging some
"out-of-the-box" thinking... That being said, I've read the FAQ, the
pertinent part:

"DRBD would not care, but most likely your filesystem will be confused
because it will not be aware about changes in the underlying device.
This in general means that it cannot work, not with ext2, ext3,
reiserFS, JFS or XFS. If you need not just a mirrored, but a shared
filesystem, use GFS or OpenGFS for example. But these are much slower."

In this case there is no "filesystem", we are accessing the partition
directly, so if DRBD truly doesn't care...???

Of course it does go on to say:

"This is the reason why DRBD does not allow mounting the secondary."

Is this arbitrary limitation really enforced?

Thanks,
Josh


> -----Original Message-----
> From: Michael Hoennig [mailto:michael at hostsharing.net]
> Sent: Wednesday, June 23, 2004 12:24 AM
> To: Josh McAllister
> Subject: RE: [DRBD-user] read-only access on Secondary for MySQL
(InnoDB)
> Raw Partition?
> 
> HI Josh,
> 
> >I'm aware of MySQL's replication... though I've had some problems in
the
> past with replication breaking under various circumstances, and I
don't
> fully trust it. Should I take "I'd not bother" to mean that what I'm
> asking is not feasible, not reliable, or that it has not been tried?
> 
> it cannot work, see FAQ on drbd.org.
> 
>       Michael