$home full? or quota enabled?


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers $home full? or quota enabled?
# 1  
Old 10-27-2008
Question 1024 byte-limit on files in $HOME/.?

I'm having trouble setting up passwordless ssh; specifically - I can only setup 2 remote hosts because when I try to add another to my known_hosts file it just won't. More investigation reveals various errors relating to 'No space left on device'.

There is plenty of free disk space; user quotas are not enabled, but yet there seems to be a very small disk quota applying to my $home directory which is affecting the $home/.ssh directory and therefore known_hosts.

I can get su on this machine, and have tried various stuff such as:
quota -v
repquota -va
df (etc)

But no go so far. Any clues? Or anyone experienced something similar?

I should point out I did not setup this SunOS machine and haven't been using it for long, so I may have missed something noobish but haven't had much luck trawling through the forums for answers.
Also, while I cannot append onto known_hosts I can create other files in the folder which contain the data I want to append to known_hosts. So it seems like a disk-usage-per-file-quota or some such bs, rather than a hard 'byte' limit on my $home folder.
So far known_hosts has 2 entries in it, making it a whopping 800 bytes long.

Last edited by dan-e; 10-27-2008 at 08:49 PM.. Reason: update title based on progress
# 2  
Old 10-27-2008
Strange alright! Have you tried renaming and recreating it or anything?
# 3  
Old 10-27-2008
Lightbulb ungh... talk to me unix... please...

Ya, gave that a go, no joy. But here's some new news - I can't make a file > 1024 bytes?? I can make a file 1024 bytes but can't add one more character on to it. Doesn't matter where the file is located in $HOME.

Any clues to that end?

This problem is the reason I posted a previous question here, although at the time I didn't realise it was related. I would really like to smash this problem in the face with a sledgehammer once I know what is going on Smilie.

Here's da proof:
Code:
qmgt1#pwd                                                             |
/users/d269836                                                        |
qmmm1#ls -Rl                                                          |
.:                                                                    |
total 12                                                              |
-rw-------   1 d269836  other        748 Oct 22 12:09 .bash_history   |
-rw-r--r--   1 d269836  other        136 Aug 15 09:04 local.cshrc     |
-rw-r--r--   1 d269836  other        157 Aug 15 09:04 local.login     |
-rw-r--r--   1 d269836  other        175 Oct 21 11:46 local.profile   |
-rw-r--r--   1 d269836  other        180 Oct 21 11:35 .profile        |
drwx------   2 d269836  other        512 Oct 27 15:45 .ssh            |
                                                                      |
./.ssh:                                                               |
total 8                                                               |
-rw-r--r--   1 d269836  other        223 Oct 21 11:41 authorized_keys | <= 2133 bytes in .ssh
-rw-------   1 d269836  other        887 Oct 21 11:41 id_rsa          |
-rw-r--r--   1 d269836  other        223 Oct 21 11:41 id_rsa.pub      |
-rw-r--r--   1 d269836  other        800 Oct 27 13:18 known_hosts     |
                                                                      |
qmmm1#rm -r .ssh                                                      | <= Free up 2133 bytes
qmmm1#ls -Rl                                                          |
.:                                                                    |
total 10                                                              |
-rw-------   1 d269836  other        748 Oct 22 12:09 .bash_history   |
-rw-r--r--   1 d269836  other        136 Aug 15 09:04 local.cshrc     |
-rw-r--r--   1 d269836  other        157 Aug 15 09:04 local.login     |
-rw-r--r--   1 d269836  other        175 Oct 21 11:46 local.profile   |
-rw-r--r--   1 d269836  other        180 Oct 21 11:35 .profile        |
qmmm1#cat > out.txt                                                   | <= Make dummy file
====================================================================  |
====================================================================  |
====================================================================  |...try to fill it up...
====================================================================  |
====================================================================  |
====================================================================  |
qmmm1#cat out.txt >>out2.txt                                          |
qmmm1#cat out.txt >>out2.txt                                          |
qmmm1#cat out.txt >>out2.txt                                          |
cat: write error: No space left on device                             | <= ooh it's full.
qmmm1#ls -aRl                                                         |
.:                                                                    |
total 18                                                              |
drwxr-xr-x   2 d269836  other        512 Oct 28 09:05 .               |
drwxr-xr-x  57 root     other       1024 Aug 15 09:04 ..              |
-rw-------   1 d269836  other        748 Oct 22 12:09 .bash_history   |
-rw-r--r--   1 d269836  other        136 Aug 15 09:04 local.cshrc     |
-rw-r--r--   1 d269836  other        157 Aug 15 09:04 local.login     |
-rw-r--r--   1 d269836  other        175 Oct 21 11:46 local.profile   |
-rw-r--r--   1 d269836  other        828 Oct 28 09:06 out2.txt        | <= 1242 bytes total in both 'out' files
-rw-r--r--   1 d269836  other        414 Oct 28 09:05 out.txt         |
-rw-r--r--   1 d269836  other        180 Oct 21 11:35 .profile        |
qmmm1#cat >> out2.txt                                                 | <= Lets bring out2.txt up to 1024 bytes,
=================================================                     |    total new data is 1438 bytes.
=================================================                     |
=================================================                     |
=================================================                     |
qmmm1#ls -l                                                           |
total 10                                                              |
-rw-r--r--   1 d269836  other        136 Aug 15 09:04 local.cshrc     |
-rw-r--r--   1 d269836  other        157 Aug 15 09:04 local.login     |
-rw-r--r--   1 d269836  other        175 Oct 21 11:46 local.profile   |
-rw-r--r--   1 d269836  other       1024 Oct 28 09:13 out2.txt        | <= It's happy at 1024 bytes
-rw-r--r--   1 d269836  other        414 Oct 28 09:05 out.txt         |
qmmm1#cat >>out2.txt                                                  |
=cat: output error (0/1 characters written)                           |
No space left on device                                               | <= ? But won't get any bigger...
qmmm1#                                                                | Note there should be at least 695 usable bytes
                                                                      | left (2133 bytes freed earlier minus 1438 bytes
                                                                      | created just now)


Last edited by dan-e; 10-27-2008 at 08:47 PM.. Reason: typo
# 4  
Old 10-28-2008
ahhh, well I still haven't figured out what is going on but I have made a successful workaround. From wasting about 5 hours trying different commands etc, I noticed that my .bash_history file grew to be > 1024 bytes. Woohoo. So I:
1. manually rebuilt my known_hosts file outside of Unix (ahh, the splendour), including the new entry I needed in there which was taking the file > 1024 bytes.
2. and then (back in unix) moved the .bash_history file over the top of known_hosts
3. vi known_hosts
4. Paste (insert) rebuilt contents from Windows editor > known_hosts
5. Deleted the 'history' junk still sitting in known_hosts, and saved.

I can now grow known_hosts up to 2047 bytes. And I still can't take any other file over the 1024 byte boundary.

The trick to all this seemed to be 2 parts - (1) acquiring a file 'out of the heavens' in $home which was > 1024 bytes long, and (2) ensuring that the file never fell below the 1024 byte boundary. I effectively pushed this file around until I had moved it+renamed it+modified the contents to my purposes.

This reeks of old-skool hack. I really need to know what is causing this, any suggestions more than welcome.

Ps: Something in my head is sqeaking "something to do with a bug in user account creation in unix... you have to make a file of a certain size in the users folder and then remove it or it causes this problem later on or something"

Last edited by dan-e; 10-28-2008 at 12:51 AM.. Reason: more info
# 5  
Old 10-28-2008
What OS revision (cat /etc/release) and architecture (uname -a) are we dealing with here?

What type of filesystem is /users (mount -v | grep users)? If it is NFS mounted or automounted, have you checked the behaviour on the server where it really resides?
# 6  
Old 10-30-2008
Java

Quote:
Originally Posted by Annihilannic
What OS revision (cat /etc/release)
qmmm1#cat /etc/release
Solaris 9 s9_58shwpl3 SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 15 April 2002

Quote:
Originally Posted by Annihilannic
and architecture (uname -a) are we dealing with here?
qmmm1#uname -a
SunOS qmmm1 5.9 Generic_112233-04 sun4u sparc SUNW,Sun-Blade-100

Quote:
Originally Posted by Annihilannic
What type of filesystem is /users (mount -v | grep users)? If it is NFS mounted or automounted, have you checked the behaviour on the server where it really resides?
mount -v | grep users gives nothing; as mount -v doesn't display any details about /users? df also doesn't show the /users folder; but it does show / which is (/dev/disk/c0t0d0s0)

Here is the output from mount -v:
qmmm1#mount -v
/dev/dsk/c0t0d0s0 on / type ufs read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=2200000 on Tue Oct 28 07:07:07 2008

/dev/dsk/c0t0d0s5 on /usr type ufs read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=2200005 on Tue Oct 28 07:07:08 2008

/proc on /proc type proc read/write/setuid/dev=3b40000 on Tue Oct 28 07:07:05 2008

mnttab on /etc/mnttab type mntfs read/write/setuid/dev=3c00000 on Tue Oct 28 07:07:05 2008

fd on /dev/fd type fd read/write/setuid/dev=3c40000 on Tue Oct 28 07:07:09 2008

/dev/dsk/c0t0d0s3 on /var type ufs read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=2200003 on Tue Oct 28 07:07:17 2008

swap on /var/run type tmpfs read/write/setuid/xattr/dev=1 on Tue Oct 28 07:07:17 2008

/dev/dsk/c0t0d0s4 on /opt type ufs read/write/setuid/intr/largefiles/logging/xattr/onerror=panic/dev=2200004 on Tue Oct 28 07:07:20 2008

swap on /tmp type tmpfs read/write/setuid/xattr/dev=2 on Tue Oct 28 07:07:20 2008

Also: I have since been able to create other files > 1024 bytes large. I did this by creating short dummy files, and then cat'ing with a wildcard and redirecting output to another dummy file (which now contains the contents of all the other files). I had to continue doing this iteratively to build up the size of the largest dummy file. I know this doesn't help much - I was trying everything I could think of so I can't really reproduce what I did. I am now at the stage where I seem to have hit a hard-limit on my $HOME folder, as I have filled it with dummy files that I can later bastardize for my needs as I did with .bash_history. This problem is weird, but I've got a strong feeling I came across it years ago... I just can't remember the cause!
# 7  
Old 10-30-2008
Okay, so it does sound like /users is on the root filesystem, which is probably a Bad Thing (TM). It's unusual that you don't have a separate /export/home filesystem, which is the normal location of users' home directories on Solaris.

For completeness can we also see the output of df -k /users and df -i /users (or df -o i if the latter is invalid for Solaris 9, it certainly is on 10, to my surprise). Also, is there definitely no reference to /users in /etc/auto_master?
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. What is on Your Mind?

The C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer

Retro Games has announced that the C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer fan, available December 2019. See also: CNN: Iconic 80s computer The Commodore 64 to return with fully-functional keyboard YouTube: The C64 | Trailer ... (2 Replies)
Discussion started by: Neo
2 Replies

2. AIX

100% Inode full with only 67% FS full.

AIX Version 6.1 and 7.1. I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device. It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies

3. Shell Programming and Scripting

cp -p /home/* home/exp/*.date not working please help

:( ---------- Post updated at 01:51 AM ---------- Previous update was at 01:50 AM ---------- Not working ---------- Post updated at 02:04 AM ---------- Previous update was at 01:51 AM ---------- cp -p /home/* home/exp/*.`date` i am using this (4 Replies)
Discussion started by: rishiraaz
4 Replies

4. Linux

Error: Encryption support not enabled

Hi when I run the following GET commad: ./snmpget -m ALL -M /data/net/naamab/snmp/snmp_mib/ -v 3 -a MD5 -l authPriv -u test1 -A welcome1 -x DES -X privpass 127.0.0.1 NOVELSAT-MODULATOR-MIB::nsModLineCMMode.0 -d I get the error: Encryption support not enabled. snmpget: USM encryption... (1 Reply)
Discussion started by: naamabm
1 Replies

5. Solaris

see if async i/o is enabled in Solaris 9

Hi guys. This may be a stupid question but I am trying to see if my Solaris 9 server has async i/o enabled... Is there a quick way to determine this? Thanks in advance. (1 Reply)
Discussion started by: jamie_collins
1 Replies

6. UNIX for Dummies Questions & Answers

know a particular user is disabled or enabled

Hi all, i had 500 users how can i know whether user is disabled or enabled Thanks, kalyan (8 Replies)
Discussion started by: kalyan212
8 Replies

7. HP-UX

st_san_safe enabled

$ uname -a HP-UX vfauh203 B.11.11 U 9000/800 486452371 unlimited-user license SCSI TAPE: dev = 0xcd520000 Failed open - st_san_safe enabled () is there any tools i can run to further investigate this err0r i received from syslog.log ? im new to hp-ux thanks (1 Reply)
Discussion started by: libchk
1 Replies

8. IP Networking

how we can find whether net is enabled or not

how we can find whether net is enabled or not with out using ping is there anyway please guide me thanku ,in advance sree (1 Reply)
Discussion started by: phani_sree
1 Replies

9. UNIX for Dummies Questions & Answers

Account creation Sudo enabled

Hi, how to create account with the following be cron enabled only accessible via sudo (1 Reply)
Discussion started by: vilves
1 Replies
Login or Register to Ask a Question