Re: ENDB and NFS?
"Peter T. Breuer" <[email protected]>
| Newsgroups | gmane.linux.enbd.general |
|---|---|
| Message-ID | <[email protected]> |
"Also sprach Marc G.:" > I'd like to create an ENBD device that is actually a NFS mounted directory. > Will this work? Hmm. Depends what you mean. > The idea is to utilize ENBD to migrate a bunch of data (120GB) from a local > disk setup to the NFS server's disks using mirroring. > > So the server the data currently resides on would "see' the NFS (Netapp) > mounted volume as the ENBD device so that the server could then mirror > it; thereby "replicating' the local "disk" with the ENBD/NFS "disk". > > Is this feasible? I don't understand! Enbd resources can be files, or anything else that responds to read/write/seek commands, such as hard disk partitions. You'll have to explain anything else you have in mind to me. ENBD provides a block device at the client end. Saying things like "the server ... would 'see' the NFS (Netapp) mounted volume as the ENBD device" doesn't make sense, since enbd devices are produced at the client end, via a kernel module. At the enbd server end, the server requires a resource it can read write and seek on. An NFS import mount (if that is what you mean by "mounted volume" - I don't know what the "Netapp" means, since I thought that was NCP-related stuff) will not fill the bill, since you cannot read write and seek on it. OTOH, a file on a NFS import will do fine as an enbd resource, though I don't see much sense in it! Peter