From: Richard C. <rch...@aa...> - 2009-09-29 05:29:08
|
Hi Jamie You have allowed multiple tmpfs mounts in the new release of webmin after I requested this. Many thanks. I have been trying to mount a second tmpfs as /tmp using webmin - and have encountered some problems I don't fully understand.... 1) I was trying to use the "Maximum Filesystem Size" parameter in the tmpfs specific options to limit the size each of the tmpfs mounts could go to. The webmin page doesn't specify what units the size parameter should use - but "man mount" suggests it should be in "bytes". I tried using large numbers (100000000) - but webmin seemed to error with anything over 2000 - so I guessed maybe webmin was assuming megabytes and converting. However - the webmin parameter seems to go directly into fstab - and I'm not sure what units are assumed in fstab. Either way - I couldn't get any sensible limit to my filesystem size using that parameter. Instead I used the "Maximum Blocks Available" parameter - and that seemed to work OK. 2) At one stage - I got webmin into a state that I couldn't change a bad parameter. I had a Max filesystem size set to "500". I'm guessing that this was so small that the mount failed at boot time - but webmin thought the filesyatem "/tmp" was mounted. Any attempt to change the "500" to "unlimited" caused an error either because webmin said the filesystem is already mounted - or because it said that it couldn't be dismounted - and it refused to save the changes I made. In the end - I had to manually edit fstab - and the problem was resolved. My suggestions: 1) Add a hyperlink to the tmpfs specific options to document what units are required for the various parameters: 2) There seems to be something wrong in webmin to cause it to reject large values for the Maximum filesystem size parameter. 3) Can the order it does things be changed so that it is possible to save changes to parameters even if the mount/dismount fails? This problem arises with filesystems that are normally only mounted at boot time. Hope this helps. Richard. |
From: Jamie C. <jca...@we...> - 2009-09-29 20:30:46
|
On 28/Sep/2009 22:28 Richard Chapman <rch...@aa...> wrote .. > Hi Jamie > > You have allowed multiple tmpfs mounts in the new release of webmin > after I requested this. Many thanks. I have been trying to mount a > second tmpfs as /tmp using webmin - and have encountered some problems I > don't fully understand.... > > 1) I was trying to use the "Maximum Filesystem Size" parameter in the > tmpfs specific options to limit the size each of the tmpfs mounts could > go to. The webmin page doesn't specify what units the size parameter > should use - but "man mount" suggests it should be in "bytes". I tried > using large numbers (100000000) - but webmin seemed to error with > anything over 2000 - so I guessed maybe webmin was assuming megabytes > and converting. However - the webmin parameter seems to go directly into > fstab - and I'm not sure what units are assumed in fstab. Either way - I > couldn't get any sensible limit to my filesystem size using that > parameter. Instead I used the "Maximum Blocks Available" parameter - and > that seemed to work OK. > > 2) At one stage - I got webmin into a state that I couldn't change a bad > parameter. I had a Max filesystem size set to "500". I'm guessing that > this was so small that the mount failed at boot time - but webmin > thought the filesyatem "/tmp" was mounted. Any attempt to change the > "500" to "unlimited" caused an error either because webmin said the > filesystem is already mounted - or because it said that it couldn't be > dismounted - and it refused to save the changes I made. In the end - I > had to manually edit fstab - and the problem was resolved. > > My suggestions: > 1) Add a hyperlink to the tmpfs specific options to document what units > are required for the various parameters: > 2) There seems to be something wrong in webmin to cause it to reject > large values for the Maximum filesystem size parameter. > 3) Can the order it does things be changed so that it is possible to > save changes to parameters even if the mount/dismount fails? This > problem arises with filesystems that are normally only mounted at boot time. Hi Richard, Those are good suggestions .. but what is the error you are getting from Webmin when you try to enter a large tmpfs size? - Jamie |
From: Richard C. <rch...@aa...> - 2009-10-01 04:54:52
|
Hi Jamie Sorry I didn't include the error before - but here it is: Failed to save mount : Remount failed : mount: /tmp not mounted already, or bad option I still get this if I try to apply a filesystem size limit to the existing tmpfs filesystem. If I leave it unlimited - I don't get the error. Richard. Jamie Cameron wrote: > On 28/Sep/2009 22:28 Richard Chapman <rch...@aa...> wrote .. > >> Hi Jamie >> >> You have allowed multiple tmpfs mounts in the new release of webmin >> after I requested this. Many thanks. I have been trying to mount a >> second tmpfs as /tmp using webmin - and have encountered some problems I >> don't fully understand.... >> >> 1) I was trying to use the "Maximum Filesystem Size" parameter in the >> tmpfs specific options to limit the size each of the tmpfs mounts could >> go to. The webmin page doesn't specify what units the size parameter >> should use - but "man mount" suggests it should be in "bytes". I tried >> using large numbers (100000000) - but webmin seemed to error with >> anything over 2000 - so I guessed maybe webmin was assuming megabytes >> and converting. However - the webmin parameter seems to go directly into >> fstab - and I'm not sure what units are assumed in fstab. Either way - I >> couldn't get any sensible limit to my filesystem size using that >> parameter. Instead I used the "Maximum Blocks Available" parameter - and >> that seemed to work OK. >> >> 2) At one stage - I got webmin into a state that I couldn't change a bad >> parameter. I had a Max filesystem size set to "500". I'm guessing that >> this was so small that the mount failed at boot time - but webmin >> thought the filesyatem "/tmp" was mounted. Any attempt to change the >> "500" to "unlimited" caused an error either because webmin said the >> filesystem is already mounted - or because it said that it couldn't be >> dismounted - and it refused to save the changes I made. In the end - I >> had to manually edit fstab - and the problem was resolved. >> >> My suggestions: >> 1) Add a hyperlink to the tmpfs specific options to document what units >> are required for the various parameters: >> 2) There seems to be something wrong in webmin to cause it to reject >> large values for the Maximum filesystem size parameter. >> 3) Can the order it does things be changed so that it is possible to >> save changes to parameters even if the mount/dismount fails? This >> problem arises with filesystems that are normally only mounted at boot time. >> > > Hi Richard, > > Those are good suggestions .. but what is the error you are getting > from Webmin when you try to enter a large tmpfs size? > > - Jamie > > > |
From: Jamie C. <jca...@we...> - 2009-10-02 04:51:07
|
Odd, I am not seeing these errors. Which OS are you running Webmin on there? I tested with tmpfs on Linux.. - Jamie On 30/Sep/2009 21:54 Richard Chapman <rch...@aa...> wrote .. > Hi Jamie > > Sorry I didn't include the error before - but here it is: > Failed to save mount : Remount failed : > mount: /tmp not mounted already, or bad option > > I still get this if I try to apply a filesystem size limit to the > existing tmpfs filesystem. If I leave it unlimited - I don't get the error. > > Richard. > > Jamie Cameron wrote: > > On 28/Sep/2009 22:28 Richard Chapman <rch...@aa...> wrote .. > > > >> Hi Jamie > >> > >> You have allowed multiple tmpfs mounts in the new release of webmin > >> after I requested this. Many thanks. I have been trying to mount a > >> second tmpfs as /tmp using webmin - and have encountered some problems I > >> don't fully understand.... > >> > >> 1) I was trying to use the "Maximum Filesystem Size" parameter in the > >> tmpfs specific options to limit the size each of the tmpfs mounts could > >> go to. The webmin page doesn't specify what units the size parameter > >> should use - but "man mount" suggests it should be in "bytes". I tried > >> using large numbers (100000000) - but webmin seemed to error with > >> anything over 2000 - so I guessed maybe webmin was assuming megabytes > >> and converting. However - the webmin parameter seems to go directly into > >> fstab - and I'm not sure what units are assumed in fstab. Either way - I > >> couldn't get any sensible limit to my filesystem size using that > >> parameter. Instead I used the "Maximum Blocks Available" parameter - and > >> that seemed to work OK. > >> > >> 2) At one stage - I got webmin into a state that I couldn't change a bad > >> parameter. I had a Max filesystem size set to "500". I'm guessing that > >> this was so small that the mount failed at boot time - but webmin > >> thought the filesyatem "/tmp" was mounted. Any attempt to change the > >> "500" to "unlimited" caused an error either because webmin said the > >> filesystem is already mounted - or because it said that it couldn't be > >> dismounted - and it refused to save the changes I made. In the end - I > >> had to manually edit fstab - and the problem was resolved. > >> > >> My suggestions: > >> 1) Add a hyperlink to the tmpfs specific options to document what units > >> are required for the various parameters: > >> 2) There seems to be something wrong in webmin to cause it to reject > >> large values for the Maximum filesystem size parameter. > >> 3) Can the order it does things be changed so that it is possible to > >> save changes to parameters even if the mount/dismount fails? This > >> problem arises with filesystems that are normally only mounted at boot time. > >> > > > > Hi Richard, > > > > Those are good suggestions .. but what is the error you are getting > > from Webmin when you try to enter a large tmpfs size? > > > > - Jamie |