我有一些Vagrant共享文件夹的问题,我的基本系统是Ubuntu 13.10桌面.
我不明白为什么我有这个错误是没有正确配置的东西？是NFS问题还是Virtualbox Guest Additions？我尝试过不同的盒子,但同样的问题.
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:
mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` /vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant /vagrant
以下是完整的流程vagrant up:
$ vagrant up
Bringing machine 'default' up …我在挂起的Linux机器上有一个NFS挂载的目录.我试图强制卸载,但它似乎不起作用:
$ umount -f /mnt/data
$ umount2: Device or resource busy
$ umount: /mnt/data: device is busy
如果我输入" mount",似乎该目录不再挂载,但如果我执行" ls /mnt/data" 它会挂起,如果我尝试删除挂载点,我会得到:
$ rmdir /mnt/data
rmdir: /mnt/data: Device or resource busy
除了重启机器之外,还有什么可以做的吗？
我需要转换int为byte[]一种方法来做它是使用BitConverter.GetBytes().但我不确定这是否符合以下规范:
XDR带符号整数是一个32位数据,它编码[-2147483648,2147483647]范围内的整数.整数用二进制补码表示.最高和最低有效字节分别为0和3.整数声明如下:
资源: RFC1014 3.2
我怎样才能进行满足上述规范的int到byte转换？
我正在尝试使用这些说明设置Discourse开发环境.但是,当我运行Vagrant时,我得到错误:
NFS报告您的导出文件无效.在对文件进行任何更改之前,Vagrant会进行此检查.请更正以下问题并执行"vagrant reload":
无法打开/ etc/exports
我查了一下,而且我没有etc/exports文件夹,所以我创建了一个并运行了vagrant reload.这让我:
/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/hosts/bsd/host.rb:146:in
read': Is a directory - /etc/exports (Errno::EISDIR) from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/hosts/bsd/host.rb:146:innfs_prune'来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/ plugins/synced_folders/nfs/synced_folder.rb:68:incleanup' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/synced_folder_cleanup.rb:24:inblock in call'from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/synced_folder_cleanup.rb:22:ineach_key' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/synced_folder_cleanup.rb:22:in来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:incall' .1/lib/vagrant/action/warden.rb:34:call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:118:in来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in来电'来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/env_set.rb:19:in来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4. 1/lib/vagrant/action/warden.rb:34:call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/builtin/provision.rb:52:in来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:13:incall'来自/ Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/set_name.rb:19:in来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34 :call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in来自/Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:34:incall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/plugins/providers/virtualbox/action/check_accessible.rb:18:in来自/ Applications/Vagrant/embedded/gems/gems/vagrant -1.4.1/lib/vagrant/action/warden.rb:34:inizeize_actioncall' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.1/lib/vagrant/action/warden.rb:95:in' …
我在一台位于NFS上的Linux机器上有一个10 GB的仓库.第一次git status需要36分钟,之后git status需要8分钟.似乎Git依赖于操作系统来缓存文件.只有第一个git命令commit,status包括打包/重新包装整个回购需要很长时间才能获得巨大的回购.我不确定你是否曾经使用git status过这么大的回购,但有没有人遇到过这个问题？
我已经试过git gc,git clean,git repack但所花费的时间仍是/几乎是相同的.
子模块或任何其他概念,比如将repo打成较小的那些有帮助吗？如果是这样,那么最好分割更大的回购.有没有其他方法可以改善大型仓库上git命令的时间？
我最近使用inotify创建了一个Dropbox系统,用于查看在特定目录中创建的文件.我正在观看的目录是从NFS服务器挂载的,而inotify的行为与我预期的不同.考虑以下场景:在机器A上运行inotify脚本,观察/ some/nfs/dir/also/visible/to/B.
- 使用机器A在/ some/nfs/dir/also/visible/to/B中创建文件,脚本按预期运行.使用机器B执行相同的操作,不会通知脚本有关目录中丢弃的新文件.
- 当在NFS服务器上运行脚本时,从机器A和机器B创建文件时会收到通知.
这是我用来访问inotofy的包中的错误,还是这个预期的行为？
问候,
安德鲁
我正在一个由Node提供支持的网站上工作.所以我创建了一个简单的Dockerfile,将我的站点文件添加到容器的FS,安装Node并在运行容器时运行应用程序,暴露私有端口80.
但是,如果我想更改该应用程序的文件,我已重建容器映像并重新运行它.这需要几秒钟.
是否有一种简单的方法来实现某种"实时同步",例如NFS,让我的主机系统的应用程序文件与正在运行的容器中的应用程序文件保持同步？
这样我只需重新启动它就可以应用更改,甚至更好,如果我使用类似的东西supervisor,它将自动完成.
有谁知道如何在带有centos基础图像的docker容器内安装nfs共享？我试过这个命令:
mount server:/dir /mount/point
并得到下一个错误:
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
当我尝试使用-o nolock选项时,错误是:
mount.nfs: Operation not permitted
有没有办法将Linux目录从不同的PC安装到本地Linux PC？怎么样？