Sponsored Content
Operating Systems AIX F7fa22c9 i o sysj2 unable to allocate space in file system Post 302750643 by ranjithm on Wednesday 2nd of January 2013 05:52:18 AM
Old 01-02-2013
F7fa22c9 i o sysj2 unable to allocate space in file system

F7FA22C9 I O SYSJ2 UNABLE TO ALLOCATE SPACE IN FILE SYSTEM

Moderator's Comments:
Mod Comment edit by bakunin: until you are willing to phrase a decent question i am unwilling to tolerate such a spammed thread here.

- Thread closed -

Last edited by bakunin; 01-02-2013 at 07:26 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

unable to allocate enough cells for gray scale

Hi, I tried to install a software (written in C) and run it on a sun machine. It is displaying the error: unable to allocate enough cells for gray scale. I closed all other apllications and set background to black to minimize usage of cells. But it is diaplaying the same error. Plz help... (1 Reply)
Discussion started by: raz
1 Replies

2. UNIX for Advanced & Expert Users

How to re-allocate disk space on solaris 10

I am not very good at UNIX and seek help here. I tried to install Oracle 10g on a 64 bit Sun sparc machine with solaris 10 as OS. After I installed solaris 10, the current file system on the machine looks like this: /dev/dsk/c0t0d0s0 5104758 4854293 199418 97% / /devices ... (2 Replies)
Discussion started by: duke0001
2 Replies

3. UNIX for Advanced & Expert Users

How to allocate swap space?

Hi all, I would like to know how i can mount swap on /tmp at boot time, I mean even before the actual script that does the mounting kicks in? i tried this mount -F tmpfs swap /tmp (nothing happens it just hangs during the booting) I also tried this /usr/lib/fs/tmpfs/mount swap /tmp... (3 Replies)
Discussion started by: wrapster
3 Replies

4. UNIX for Dummies Questions & Answers

allocate more space to /home

Hi all Is there a way to allocate more space to a partition? For example my /home is almost full , at 96% so can I move memory from lets say / to /home? df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 6190692 2571688 3304532 44% / /dev/sda2... (2 Replies)
Discussion started by: mcraul
2 Replies

5. UNIX for Advanced & Expert Users

unable to allocate enough memory

On SunOS 5.8 I get an error when starting a large Java process with over 2Gb memory. Error occurred during initialization of VM Could not reserve enough space for object heap When stopping several other Java processes we can start this process. This seems to indicate that we don't have... (11 Replies)
Discussion started by: rein
11 Replies

6. Linux

Unable to remove file using rm: Disk space is full

Hi all, My disk space is 100% full. df -k <dir> -> 100% One of my debug files consume huge amount of space and i want to remove the same to start off fresh debugs. However i'm unable to remove the file giving out the following error message: rm -f debug.out22621 rm: cannot remove... (8 Replies)
Discussion started by: Pankajakshan
8 Replies

7. UNIX for Advanced & Expert Users

Unable to clean up file system

Hi, Has anyone ever encountered the following scenario: I am working on a SUN server with solaris 10 installed and veritas managing the filesystem. One of the file systems has become full: df -kh /ossrc/dbdumps Filesystem size used avail capacity Mounted on... (6 Replies)
Discussion started by: eeidel
6 Replies

8. Solaris

Re-allocate disk space

I am running out of space, and would like to reallocate some "wasted" space. Here is what I see: > df -h Filesystem Size Used Avail Use% Mounted on /dev/dsk/c0t0d0s0 5.4G 4.5G 860M 85% / swap 2.0G 1.3M 2.0G 1% /etc/svc/volatile swap ... (4 Replies)
Discussion started by: ippy98
4 Replies

9. Solaris

Solaris file system unable to use available space

Hi, The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB. The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space. ofcourse the software... (31 Replies)
Discussion started by: iris1
31 Replies

10. Solaris

unable to allocate enough memory

On SunOS 10 get an error when starting a large Java process with over 2Gb memory. Error occurred during initialization of VM Could not reserve enough space for object heap i have 32G memory !! , swap = 31G Please any advice !!! (3 Replies)
Discussion started by: moata_u
3 Replies
sf(7D)								      Devices								    sf(7D)

NAME
sf - SOC+ FC-AL FCP Driver SYNOPSIS
sf@port,0 DESCRIPTION
The sf driver is a SCSA compliant nexus driver which supports the Fibre Channel Protocol for SCSI on Private Fibre Channel Arbitrated loops. An SBus card called the SOC+ card (see socal(7D)) connects the Fibre Channel loop to the host system. The sf driver interfaces with the SOC+ device driver, socal(7D), the SCSI disk target driver, ssd(7D), and the SCSI-3 Enclosure Services driver, ses(7D). It only supports SCSI devices of type disk and ses. The sf driver supports the standard functions provided by the SCSA interface. The driver supports auto request sense and tagged queueing by default. The driver requires that all devices have unique hard addresses defined by switch settings in hardware. Devices with conflicting hard addresses will not be accessible. FILES
/platform/architecture/kernel/drv/sf ELF kernel module /platform/architecture/kernel/drv/sf.consf driver configuration file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ SEE ALSO
luxadm(1M), prtconf(1M), driver.conf(4), socal(7D), ssd(7D) Writing Device Drivers ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.269-1996, Fibre Channel Protocol for SCSI (FCP) ANSI X3.270-1996, SCSI-3 Architecture Model (SAM) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) DIAGNOSTICS
In addition to being logged, the messages below may display on the system console. The first set of messages indicate that the attachment was unsuccessful, and will only display while the sf driver is initially attempting to attach. Each message is preceded by sf%d , where %d is the instance number of the sf device. Failed to alloc soft state Driver was unable to allocate space for the internal state structure. Driver did not attach to device, SCSI devices will be inaccessi- ble. Bad soft state Driver requested an invalid internal state structure. Driver did not attach to device, SCSI devices will be inaccessible. Failed to obtain transport handle Driver was unable to obtain a transport handle to communicate with the socal driver. Driver did not attach to device, SCSI devices will be inaccessible Failed to allocate command/response pool Driver was unable to allocate space for commands and responses. Driver did not attach to device, SCSI devices will be inaccessible. Failed to allocate kmem cache Driver was unable to allocate space for the packet cache. Driver did not attach to device, SCSI devices will be inaccessible. Failed to allocate dma handle for Driver was unable to allocate a dma handle for the loop map. Driver did not attach to device, SCSI devices will be inaccessible. Failed to allocate lilp map Driver was unable to allocate space for the loop map. Driver did not attach to device, SCSI devices will be inaccessible. Failed to bind dma handle for Driver was unable to bind a dma handle for the loop map. Driver did not attach to device, SCSI devices will be inaccessible. Failed to attach Driver was unable to attach for some reason that may be printed. Driver did not attach to device, SCSI devices will be inaccessible. The next set of messages may display at any time. The full device pathname, followed by the shorter form described above, will precede the message. Invalid lilp map The driver did not obtain a valid lilp map from the socal driver. SCSI device will be inaccessible. Target t, AL-PA x and hard The device with a switch setting t has an AL-PA x which does not match its hard address y. The device will not be accessible. Duplicate switch settings The driver detected devices with the same switch setting. All such devices will be inaccessible. WWN changed on target t The World Wide Name (WWN) has changed on the device with switch setting t. Target t, unknown device type The driver does not know the device type reported by the device with switch setting t. SunOS 5.10 27 Mar 1997 sf(7D)
All times are GMT -4. The time now is 03:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy