l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Jun 20 00:37

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] In Denial About These Hard Drive Problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] In Denial About These Hard Drive Problems

On Wed, 19 Jun 2002, Richard S. Crawford wrote:
> This afternoon I noticed that my /home partition was expanding 
> again.  Normally when I run df -h it shows /home as being filled to 52% of 
> the available space; this afternoon, though, it was up to 100%.  I was away 
> from my computer and logging in remotely so I didn't want to do anything 
> too drastic.  I just found some wine processes that were running and killed 
> them, then deleted some extra tar files that I'd accumulated, to bring 
> things down to 98% so that my computer could keep running until I could get 
> home and reboot it, which is what stopped this problem before (I never did 
> figure out what was causing it).

How big is this mounted partition and what was using up the space? What
version kernel are you using, and what filesystem type is being used on
this partition and other? What kind of drive is it (IDE/ATAPI or SCSI)

> So when I rebooted, I found some root filesystem errors, fixed them with 
> fsck /.  Then X wouldn't start.  I checked the message log and saw this error:
>          fatal error: could not open default font fixed
> (or something like that).
> Fearing nasty trouble, I decided I'd take the simpleton's way out and just 
> repair things from my installation disk.  That process complained because 
> I'd created a symbolic link to /var on a large extra partition on my hard 
> drive (it wanted me to transform the absolute symbolic link /var to a 
> relative symbolic link -- something that is outside my realm of knowledge, 
> I'm afraid, though I did try to find it in my books).

With sym links there are a few. For filesystems, they are *sort of* like
shortcuts in Windowsland (even though they are not really) and aliases in
Mac land (closer then windows land with MacOS 9 and earlier but still not
quite the same).

There are "links" to files and "symbolic links" to files

Lnks to files are much like pointers to space on a hard disk. Each pointer
uses up an "entry" on your partition's filesystem, but does not double the
size of space used by the file. 5 "hard" links to the same data (or
original file) on the same mounted filesystem/partition lead to only one
copy of that file on disk with 5 "pointers" to it. The file is not
actually deleted unless all of the links to the file are destroyed. When
the last link is destroyed, then the filesystem "forgets" where the file
was located even though the physical data is often still on disk (depends
on filesystem and settings though.)

Making hard links to folders/directories require root access and is
generally considered a "bad idea" due to risks with recursion/looping

symbolic links are not "hard links" to file. They are kind of like
redirection. A symbolic link to a file may exist even after the file it
was pointing at is deleted. This is sort of like an "alias" in a
shell. If you alias "ls" to be "ls -CF", then the alias still exists even
if "ls" is deleted. Of course, your alias (ls) will fail to run as
as "desired", but that is the way it goes. Symbolic links may span
filesystems and pass across network shares (big plus) and generally
should not cause problems to recursive directory searches (when a dir is
symlinked) unless you employ lesser known args to certain commands and
tel them to follow symlink as though they were real links (duhhhh... heh

In the world of sym links there are two common types:

Borrowing from the world of HTML and web pages, you can see a very close

Say you have /var/www as your server root and within it you have a file
"myimage.jpg" and another directory called "dir" and in "dir" you have a
file "index.html".

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.