Why the NFS client is at fault in the multi-filesystem NFS problem
In yesterday's entry , I said that theNFS clients were at fault in dealing with the duplicate inode numberproblem. Now it's time for the details, because on first look thisappears a bit odd; how can it be the client's responsibility to avoidduplicate inode numbers, when the server gives it the inode numbers?
In the NFS v3 specification ,inode numbers only appear in one spot; they're part of the fileattribute structure that the server returns for GETATTR requests.While
英劇
近日我「好不容易」才看完 Skins 的第二季,還一口氣看了兩季 Little Britain ,之後又同步開始追看 Hotel Babylon ,似乎我對英劇情有獨鍾,而且都是看舊的,真是落後於形勢。 我有時有些習慣會非常低能,例如遇到好看的電視劇,我會刻意拖延進度
Truth
Few, if any, moral philosophers would admonish
The cause of the multi-filesystem NFS export problem
There is a famous irritation with managing NFS filesystems which boilsdown to that NFS clients have to know about your filesystem boundaries.It goes like this: suppose that /home and /home/group1 are separatefilesystems and you NFS export both of them. What you would like isthat clients NFS mount /home and automatically get /home/group1 too, because this lets you transparently add /home/group2 next month.However, this doesn't work (although some systems will try hard to
不會是明信片
實在有太多理由不去買明信片了,試想像一個人忽然
抑鬱症仙丹
唉,