Sponsored Content
Operating Systems Solaris Sol11 - Error at prompt (no space left on device) Post 303008703 by psychocandy on Tuesday 5th of December 2017 04:50:55 AM
Old 12-05-2017
Sol11 - Error at prompt (no space left on device)

Code:
user1@:/$
-ksh: line 3: write to 1 failed [No space left on device]
user11@:/$
-ksh: line 3: write to 1 failed [No space left on device]
user1@:/$
-ksh: line 3: write to 1 failed [No space left on device]
user1@:/$
-ksh: line 3: write to 1 failed [No space left on device]
user1@:/$
-ksh: line 3: write to 1 failed [No space left on device]

But theres plenty of space :-

Code:
user1@:/$ df -kh
Filesystem             Size   Used  Available Capacity  Mounted on
rpool/ROOT/solaris      59G    14G        21G    41%    /
/devices                 0K     0K         0K     0%    /devices
/dev                     0K     0K         0K     0%    /dev
ctfs                     0K     0K         0K     0%    /system/contract
proc                     0K     0K         0K     0%    /proc
mnttab                   0K     0K         0K     0%    /etc/mnttab
swap                   148M   3.0M       145M     3%    /system/volatile
objfs                    0K     0K         0K     0%    /system/object
sharefs                  0K     0K         0K     0%    /etc/dfs/sharetab
fd                       0K     0K         0K     0%    /dev/fd
rpool/ROOT/solaris/var
                        59G    18G        21G    46%    /var
swap                   151M   6.4M       145M     5%    /tmp
rpool/VARSHARE          59G   3.1M        21G     1%    /var/share
rpool/export            59G    32K        21G     1%    /export
rpool/export/home       59G   438K        21G     1%    /export/home
rpool                   59G    73K        21G     1%    /rpool
rpool/VARSHARE/zones    59G    31K        21G     1%    /system/zones
rpool/VARSHARE/pkg      59G    32K        21G     1%    /var/share/pkg
rpool/VARSHARE/pkg/repositories
                        59G    31K        21G     1%    /var/share/pkg/repositories

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

no space left on device

This seems like it would be a common question, but I didn't find much that helped in a search... I have a script scheduled in my crontab that outputs to /dev/null ie: /dir/scripts/script1 > /dev/null I have recently started getting the error: cp /dir1/dir2/file.xls: No space left on... (1 Reply)
Discussion started by: kristy
1 Replies

2. UNIX for Dummies Questions & Answers

cat: write error: No space left on device

I am trying to create new files under my directory...but i getting the following message... cat: write error: No space left on device How do we handle this error. I am not getting this error when I login as the super user (3 Replies)
Discussion started by: igandu
3 Replies

3. Solaris

No space left on device

Hi all, A very strange problem I have this morning with my Solaris 8. I have a FS full, I deleted some files but the system doesn't seems to reallocate the free space (I'm using Veritas): df -k : /dev/vx/dsk/dlds02vg/dlds02oralv 4194304 4194304 0 100% /dlds02/lds/oracle ... (4 Replies)
Discussion started by: unclefab
4 Replies

4. Solaris

No space left on device

We are using this function tmpfile() : FILE *tmpfp ; if ((tmpfp = tmpfile()) == NULL) { fprintf(stderr, "%s: ERROR: init_operator(): ", ROUTINE); perror("tmpfile()"); exit(ERR_OPEN); } and the above is raising error : MSMD0603: ERROR:... (3 Replies)
Discussion started by: atiato
3 Replies

5. Solaris

No space left on device but free space and inodes are available...

hi guys, me again ;) i recently opened a thread about physical to zone migration. My zone is mounted over a "bigger" LUN (500GB) and step is now to move the old files, from the physical server, to my zone. We are talking about 22mio of files. i used rsync to do that and every time at... (8 Replies)
Discussion started by: beta17
8 Replies

6. Solaris

visudo: write error: No space left on device

Hi All, This is Sandeep Gupta, I am facing a problem with sudo command. Whenever i am executing the command "visudo" i am getting the error "visudo: write error: No space left on device". but i have checked on my Solaris Box everything is ok, i have enough free space on my box, and also... (13 Replies)
Discussion started by: Sandeepgupta
13 Replies

7. Linux

No space left on device when using rm

Hello people I have a small fileserver running busybox (very small linux distro with most essential stuff on it) and I am trying to remove some unused directories on it. When I try this: rm -R test/I get: rm: cannot remove 'test': No space left on devicedf shows: Filesystem ... (8 Replies)
Discussion started by: GTCG
8 Replies

8. HP-UX

Received error as Not enough space left on device

Hi Forum, We have observed one problem in one of our HP-UX machines which runs a software which connects the radio frequency scan devices and the scanned information is stored in the database through the same software. This software has thrown an error like "Not enough space left on the... (4 Replies)
Discussion started by: Nishant.Jvk
4 Replies

9. Linux

No space left on device while there is plenty of space available

Hello all posting here after scanning the net and tried most of the things offered still no solution that worked when I do : $ df -h Filesystem Size Used Avail Use% Mounted on footmpfs 7.9G 60K 7.9G 1% /dev tmpfs 7.9G 0 7.9G 0% /dev/shm /dev/da1 ... (3 Replies)
Discussion started by: umen
3 Replies

10. Solaris

Write to 1 failed [No space left on device] Error

Running a installation on Solaris 11 and getting error write to 1 failed If anyone can advise ? ORIGINAL_PATH="${PATH}" # prepend /usr/xpg4/bin to PATH as needed temporaryPath=`expr "${PATH}:" : '\(/usr/xpg4/bin:\)'` if then PATH="/usr/xpg4/bin:${PATH}" seem to have... (6 Replies)
Discussion started by: Mpumi
6 Replies
fb.modes(8)						     Linux frame buffer utils						       fb.modes(8)

NAME
fb.modes - frame buffer modes file DESCRIPTION
/etc/fb.modes contains an unlimited number of video mode descriptions. The general format of a video mode is: mode geometry <xres> <yres> <vxres> <vyres> <depth> timings <pixclock> <left> <right> <upper> <lower> <hslen> <vslen> options <value> endmode OPTIONS
geometry options: xres visible horizontal resolution (in pixels) yres visible vertical resolution (in pixels) vxres virtual horizontal resolution (in pixels) vyres virtual vertical resolution (in pixels) depth display depth (in bits per pixel) timing options: pixclock length of one pixel (in picoseconds) left left margin (in pixels) right right margin (in pixels) upper upper margin (in pixel lines) lower lower margin (in pixel lines) hslen horizontal sync length (in pixels) vslen vertical sync length (in pixel lines) other options: the first value of this options is the default hsync {low|high} the horizontal sync polarity vsync {low|high} the vertical sync polarity csync {low|high} the composite sync polarity extsync {false|true} enable or disable external resync. If enabled the sync timings are not generated by the frame buffer device and must be pro- vided externally instead. Note that this option may not be supported by every frame buffer device laced {false|true} enable or disable interlace. If enabled the display will be split in two frames, each frame contains only even and odd lines respectively. These two frames will be displayed alternating, this way twice the lines can be displayed and the vertical fre- quency for monitor stays the same, but the visible vertical frequency gets halved double {false|true} enable or disable doublescan. If enabled every line will be displayed twice and this way the horizontal frequency can easily be doubled, so that the same resolution can be displayed on different monitors, even if the horizontal frequency specifica- tion differs. Note that this option may not be supported by every frame buffer device INTERNALS
Generally a frame buffer display is organized as follows: +---+---------------+---+---+ | | ^ | | | | | | 5 | | | | | v | | | +---#################---+---+ | # ^ # | | | # | # | | | # | # | | | 1 # | 2 # 3 | 4 | |<->#<------+------>#<->|<->| | # | # | | | # | 6 # | | | # | # | | | # v # | | +---#################---+---+ | | ^ | | | | | | 7 | | | | | v | | | +---+---------------+---+---+ | | ^ | | | | | | 8 | | | | | v | | | +---+---------------+---+---+ 1 left margin 2 xres 3 right margin 4 horizontal sync len 5 upper margin 6 yres 7 lower margin 8 vertical sync len The area bordered with `#' is the visible display area. Horizontal and vertical frequencies can now easily be calculated, for this the sum of horizontal or vertical values are important htotal = left + xres + right + hslen vtotal = upper + yres + lower + vslen The length of one line can now be calculated with pixclock line = pixclock * htotal and we have the horizontal frequency hfreq = 1E12 / line = 1E12 / (pixclock * htotal) To get the vertical frequency vtotal must eventually adjusted. If the display is laced, vtotal must be halved or if the display is a dou- blescan one, vtotal must be doubled. Now we can calculate the length of one frame if (lace) vtotal /= 2 if (double) vtotal *= 2 frame = vtotal * line and we get also the vertical frequency vfreq = 1E12 / frame = hfreq / vtotal SEE ALSO
fbset(8), fbdev(4) local Aug 1996 fb.modes(8)
All times are GMT -4. The time now is 06:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy