Tag Info

New answers tagged

0

Your configuration is correct, you have however selected snapshot, which is zero-downtime container backup. Seemingly your LVM however isn't setup correctly so the snapshot can't be done. I would recommend to try with suspend mode. (which has very little downtime)


1

If data is available in the file system cache, then 'read' syscall will get the data, but there will be no read requests sent to the NFS server. This can happen when an application reads the same blocks several times, or when user opens the same file multiple times. You can flush the file system cache and watch the result of iostat again: # echo 3 > ...


3

no_root_squash is a server side (export) option, not a client side option. It therefore doesn't go in /etc/fstab, nor can it be specified to mount. If you think about it - why would you want a client to be able to decide "hey, I'll be root today, that'll be nice"? http://linux.die.net/man/5/exports I'd suggest though, that rather than setting ...


1

A rpc message (and NFS is rpc based service) can be split into multiple frames (chunks). Any RPC server has a limit on frame size as well as a limit on message size. "RPC: fragment too large: " indicates that NFS server got a rpc frame which is bigger than max allowed size. This message can point to a bug in the client code, server code or network issues. ...


1

It's an interesting question. It's hard to answer because it's quite variable and depends on: what your NFS server is doing. (A NAS appliance is usually going to be quite clever about caching). Why your speed was 'so slow'. In general though - it's entirely normal for a server to cache write operations. RAID write penalty is quite high*, and you can ...


2

Based on comments so far: your mount works with NFSv3, it doesn't with NFSv3. you're using local accounts. This means that the problem is most likely down to NFSv4 account handling and idmapd. What happens in NFSv3 is that your client tells the server what UID and GID you're using. What happens in NFSv4 is that they use usernames and use idmapd to map ...


0

The thing you need to think about is how up to date you need both devices to be. The nearer you get to 'real time' sync, the more difficult and expensive it gets. Fully synchronous replication options exist, but they're bandwidth intensive and very sensitive to network latency. I wouldn't normally suggest doing that on sites that are geographically ...


1

DRBD is more or less a RAID1 implementation for block device replication over networks and does sync in real-time. For high latency/low bandwidth communication using a indirect setup using DRBD proxy is recommend. When using DRBD over high latency, possible instable WAN connection, a active/passive (called primary/secondary in DRBD) setup is highly ...


6

RAID is definitely not your answer. RAID is generally for drives being used in an array in the same physical location. If you want to sync file systems across continents, then you need to use a NAS product that has some form of live mirroring capability. Most enterprise-class SAN/NAS products have this feature. Otherwise, something like lsyncd or even a ...


0

I'm not sure about with XP. However, I had a similar issue on Windows Server 2012. The solution was to enable the Network Access: Let Everyone permissions apply to anonymous users policy setting under Security Settings\Local Policies\Security Options. I found the solution on this page: http://technet.microsoft.com/en-us/library/hh509019%28v=ws.10%29.aspx


1

You should be able to mount an NFS volume on the CoreOS host. If there is no userland tools to export a filesystem from CoreOS, you can use Fedora toolbox container provided by the toolbox command.


2

Yes, that is possible and safe. Yes, that should be possible. But I recommend you to enable Amazon Load Balancer Sticky Session feature Yes, it should be possible with some caveats: you should be careful about network protocol used for accessing shared data. Subversion relies on file locking and atomic file move operations. SMB and SMB2 are known to be ...



Top 50 recent answers are included