Sponsored Content
Full Discussion: J2EE 1.4 on Solaris 8
Operating Systems Solaris J2EE 1.4 on Solaris 8 Post 51674 by pressy on Thursday 27th of May 2004 04:44:31 PM
Old 05-27-2004
...........

perhabs your filesystem is out of inodes.....

# df -F ufs -o i

greetings Preßy
 

3 More Discussions You Might Find Interesting

1. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

2. Programming

J2EE prerequisites

Hi guys, I'm going to start studding about J2EE in a couple of weeks. I have no idea about its technologies. what prerequisites do i need. I only know java and have basic knowledge about HTML. I have a solid knowledge on database. 1. Do i need java script or CSS knowledge for JSP and JSF? 2.... (1 Reply)
Discussion started by: majid.merkava
1 Replies

3. UNIX and Linux Applications

search for introduction Jboss book,for admins (no Java and J2EE dev expirence)

Hi I am searching for introduction to Jboss for admins book. I will administrate an application which runs inside Jboss. I have no Java and J2EE development experience. That means for dummies :wall: Amazon search gets to many hits: http://i.imgur.com/tCayW.png What do you recommend me?... (0 Replies)
Discussion started by: slashdotweenie
0 Replies
FREEZE_SUPER(9) 						   The Linux VFS						   FREEZE_SUPER(9)

NAME
freeze_super - lock the filesystem and force it into a consistent state SYNOPSIS
int freeze_super(struct super_block * sb); ARGUMENTS
sb the super to lock DESCRIPTION
Syncs the super to make sure the filesystem is consistent and calls the fs's freeze_fs. Subsequent calls to this without first thawing the fs will return -EBUSY. During this function, sb->s_writers.frozen goes through these values: SB_UNFROZEN File system is normal, all writes progress as usual. SB_FREEZE_WRITE The file system is in the process of being frozen. New writes should be blocked, though page faults are still allowed. We wait for all writes to complete and then proceed to the next stage. SB_FREEZE_PAGEFAULT Freezing continues. Now also page faults are blocked but internal fs threads can still modify the filesystem (although they should not dirty new pages or inodes), writeback can run etc. After waiting for all running page faults we sync the filesystem which will clean all dirty pages and inodes (no new dirty pages or inodes can be created when sync is running). SB_FREEZE_FS The file system is frozen. Now all internal sources of fs modification are blocked (e.g. XFS preallocation truncation on inode reclaim). This is usually implemented by blocking new transactions for filesystems that have them and need this additional guard. After all internal writers are finished we call ->freeze_fs to finish filesystem freezing. Then we transition to SB_FREEZE_COMPLETE state. This state is mostly auxiliary for filesystems to verify they do not modify frozen fs. sb->s_writers.frozen is protected by sb->s_umount. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 FREEZE_SUPER(9)
All times are GMT -4. The time now is 01:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy