This situation creates a need for two distinct states: an external mount, and an internal mount. This creates a dichotomy: the external mount, initiated through the OS mount command is a system administrator-driven operation that cannot be easily reversed, but GPFS needs a way to manipulate the file system accessibility in response to internal triggers. On the other hand, since GPFS is a distributed application, there are situations when a node that does not have the file system mounted, needs to read internal data structures from disk to allow the node to act as, for example, a file system manager, or a token manager. If the quorum is lost, data access is impossible no matter what the mount command output says. For instance, in order to be able to provide any data access on a given node, a node quorum must be reached, and the current node must be an active member of the cluster. There are important things to worry about that take place outside the OS kernel. GPFS, being a cluster file system, is not blessed with such simple semantics. If the OS kernel is alive, a mounted ext3 file system is accessible because all of ext3 code lives in the OS kernel. For example, an ext3 file system can either be mounted or not mounted, there is nothing in between. However, GPFS is orders of magnitude more complex than a typical local Unix file system, and that makes things more complicated. How come my file system is shown as mounted, but I cannot access any files? I have just unmounted my file system, but mmlsmount shows that it is 'internally mounted' - why? I am trying to unmount my file system, and the darn thing just will not unmount - how can I force it? Can I use the mount command provided by the OS, or do I have to use mmmount? I do not use NFS, and yet I see error messages about 'Stale NFS file handles' - why?Īt its core, GPFS is a Unix file system, and so it follows the standard Unix conventions where it comes to mount and unmount semantics. O23 - Service: (KeyIso) - Unknown owner - C:\Windows\system32\lsass.Seemingly simple concepts of 'mount' and 'unmount' often generate confusion among GPFS users. O23 - Service: InstallDriver Table Manager (IDriverT) - Macrovision Corporation - C:\Program Files (x86)\Common Files\InstallShield\Driver\1050\Intel 32\IDriverT.exe O23 - Service: Intel® Rapid Storage Technology (IAStorDataMgrSvc) - Intel Corporation - C:\Program Files (x86)\Intel\Intel® Rapid Storage Technology\IAStorDataMgrSvc.exe C:\Program Files (x86)\LogMeIn Hamachi\hamachi-2.exe O23 - Service: LogMeIn Hamachi Tunneling Engine (Hamachi2Svc) - LogMeIn Inc. O23 - Service: (Fax) - Unknown owner - C:\Windows\system32\fxssvc.exe (file missing) O23 - Service: (EFS) - Unknown owner - C:\Windows\System32\lsass.exe (file missing) O23 - Service: Desura Install Service - Desura Pty Ltd - C:\Program Files (x86)\Common Files\Desura\desura_service.exe O23 - Service: Creative Audio Service (CTAudSvcService) - Creative Technology Ltd - C:\Program Files (x86)\Creative\Shared Files\CTAudSvc.exe O23 - Service: Creative Audio Engine Licensing Service - Creative Labs - C:\Program Files (x86)\Common Files\Creative Labs Shared\Service\CTAELicensing.exe O23 - Service: Creative ALchemy AL6 Licensing Service - Creative Labs - C:\Program Files (x86)\Common Files\Creative Labs Shared\Service\AL6Licensing.exe O23 - Service: (ALG) - Unknown owner - C:\Windows\System32\alg.exe (file missing) O23 - Service: Adobe Flash Player Update Service (AdobeFlashPlayerUpdateSvc) - Adobe Systems Incorporated - C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe O23 - Service: ABBYY FineReader 9.0 PE Licensing Service (.9.0) - ABBYY (BIT Software) - C:\Program Files (x86)\Common Files\ABBYY\FineReader\9.00\Licensing\PE\NetworkLicenseServer.exe O23 - Service: ABBYY FineReader 11 PE Licensing Service (.11.0) - ABBYY - C:\Program Files (x86)\ABBYY FineReader 11\NetworkLicenseServer.exe Here's the log.Ĭ:\Program Files (x86)\Windows Live\Messenger\msnmsgr.exeĬ:\Program Files (x86)\Intel\Intel® Rapid Storage Technology\IAStorIcon.exeĬ:\Program Files (x86)\XFastUsb\XFastUsb.exeĬ:\Program Files (x86)\InstallShield Installation Information\ - C:\Program Files (x86)\Common Files\AVG Secure Search\ViProtocolInstaller\11.1.0\ViProtocol.dll
0 Comments
Leave a Reply. |