Anderson and Gary, Many thanks for your attention! I've did one test here, and works perfectly! I just have one problem, because I need to restart my gnbd_serv, and re-export the GNDB device for nodes, because I've got this error messages: Apr 4 16:40:15 xen-7 gnbd_serv[23817]: ERROR size of the exported file /dev/Vol_LVM/mycluster has changed, aborting Apr 4 16:40:15 xen-7 gnbd_serv[23817]: server process 2956 exited because of signal 11 Apr 4 16:40:15 xen-7 kernel: gnbd_serv[2956]: segfault at 000000000000000c rip 0000000000405ab0 rsp 00007fff36dcb450 error 4 Apr 4 16:41:10 xen-7 gnbd_serv[2970]: startup succeeded Apr 4 16:41:17 xen-7 gnbd_serv[2970]: got local command 0x1 Apr 4 16:41:17 xen-7 gnbd_serv[2970]: gnbd device 'cluster' serving /dev/Vol_LVM/mycluster exported with 41943040 sectors But I did another test, and this time I've just "restart" the export using: # gnbd_export -R -O # gnbd_export -c -d /dev/Vol_LVM/mycluster -e cluster And sounds like fine on the nodes... but I don't know if this process it's recommend, or if this force (-O Force unexport) can be dangerous for the filesystem... Thanks On Fri, 2008-04-04 at 14:22 -0500, Derek Anderson wrote: > You can grow the filesystem with gfs_grow, once the underlying device > has been expanded. See gfs_grow(8) for more information. -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
