A naive question, but how do people go about adding (or changing) storage in a system? In particular, how do folks change the client-vol file on an operating cluster? I would like to be able to do something like "remount" and have client-vol changes work for a particular machine and not have to search out all the open connections in order to do that update. I know the question is not a very good one, but any suggestions on how this works in practice? Thanks, Sean -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090129/153f1690/attachment.html>
At 12:15 PM 1/29/2009, Sean Davis wrote:>A naive question, but how do people go about adding (or changing) >storage in a system? In particular, how do folks change the >client-vol file on an operating cluster? I would like to be able to >do something like "remount" and have client-vol changes work for a >particular machine and not have to search out all the open >connections in order to do that update. I know the question is not >a very good one, but any suggestions on how this works in practice?unfortunately, gluster doesn't support -o remount just yet. what I do is unmount/remount the filesystem. which is a tad inconvenient, but here's a script that was posted to the list a while ago to help find processes that are hanging on a mountpoint: --whodir-- #!/bin/sh DIR=$1 find /proc 2>/dev/null | grep -E 'cwd|exe' | xargs ls -l 2>/dev/null | grep "> $DIR" | sed 's/ */ /g' | cut -f8 -d' ' | cut -f3 -d/ | sort | uniq | while read line; do echo $line $(cat /proc/$line/cmdline); done
At 12:15 PM 1/29/2009, Sean Davis wrote:>A naive question, but how do people go about adding (or changing) >storage in a system? In particular, how do folks change the >client-vol file on an operating cluster? I would like to be able to >do something like "remount" and have client-vol changes work for a >particular machine and not have to search out all the open >connections in order to do that update. I know the question is not >a very good one, but any suggestions on how this works in practice?unfortunately, gluster doesn''t support -o remount just yet. what I do is unmount/remount the filesystem. which is a tad inconvenient, but here''s a script that was posted to the list a while ago to help find processes that are hanging on a mountpoint: --whodir-- #!/bin/sh DIR=$1 find /proc 2>/dev/null | grep -E ''cwd|exe'' | xargs ls -l 2>/dev/null | grep "> $DIR" | sed ''s/ */ /g'' | cut -f8 -d'' '' | cut -f3 -d/ | sort | uniq | while read line; do echo $line $(cat /proc/$line/cmdline); done
On Thu, Jan 29, 2009 at 3:25 PM, Keith Freedman <freedman at freeformit.com>wrote:> At 12:15 PM 1/29/2009, Sean Davis wrote: > >> A naive question, but how do people go about adding (or changing) storage >> in a system? In particular, how do folks change the client-vol file on an >> operating cluster? I would like to be able to do something like "remount" >> and have client-vol changes work for a particular machine and not have to >> search out all the open connections in order to do that update. I know the >> question is not a very good one, but any suggestions on how this works in >> practice? >> > > unfortunately, gluster doesn't support -o remount just yet. > what I do is > > unmount/remount the filesystem. > which is a tad inconvenient, but here's a script that was posted to the > list a while ago to help find processes that are hanging on a mountpoint: > > --whodir-- > #!/bin/sh > DIR=$1 > find /proc 2>/dev/null | grep -E 'cwd|exe' | xargs ls -l 2>/dev/null | grep > "> $DIR" | sed 's/ */ /g' | cut -f8 -d' ' | cut -f3 -d/ | sort | uniq | > while read line; do echo $line $(cat /proc/$line/cmdline); done >Thanks, Keith. I had even archived that script in my email but promptly forgot that I had done so. We don't have many users, so that will probably work just fine. Sean -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20090129/7523e7a3/attachment.html>
At 12:30 PM 1/29/2009, Sean Davis wrote:>Thanks, Keith. I had even archived that script in my email but >promptly forgot that I had done so. > >We don''t have many users, so that will probably work just fine.I''ve found that if I do this in a low period and am very quick, it goes unnoticed even by the external monitoring. the key for me is to have the "umount /MOUNTPOINT; mount /MOUNTPOINT" in the history so I can get to it quickly, then see what processes need to be stopped and started. good luck.