Fw: Help:FW Harddisk has no space!
J Leung
ckjleung at yahoo.com
Fri May 30 10:46:07 PDT 2003
Dear Stanley,
good to hear what you found using fsck. I still don't
have a sidewinder machine next to me until now... so
I'm not quite sure what the option -y will do. I
searched the Internet, (I never had problem on file
system until now, so I never use those option before.)
-y will assume all the interative question to yes. Why
don't you use it Interatively, it sounds more save to
me. Anyway, the command looks okay for me, but do the
following:
1) make a copy (backup) of all the files in /home
before the operation. In the case of data lose in
/home after the operation.
2) reboot the system after the command. (because you
will do the operation on a mounted file system, and it
will damage the file system in some way. the best
method is unmount it before the operation, then you
will be save. The problem is I'm not sure how to
unmount /home partition. So, backup and reboot.)
if possible, I would like to have the log for fsck
command (before and after the operation) you've got
for reference, thanks.
Good luck.
Jackson
--- Stanley Wong <questions at freebsd.org> wrote:
> Dear Jackson,
>
> I have take a look in the function fsck, and run it
> already. Luckly, it
> shows me a inode error found in the /home partition
> and i think i should use
> "fsck./home -y". Do you thank it is ok?
>
> Please mail back me asap, i plan to run it tomorrow
> , thank you!
>
> Stanley
> ----- Original Message -----
> From: "J Leung" <ckjleung at yahoo.com>
> To: "Stanley Wong" <stanley.wong at rexcapital.com.hk>
> Sent: Friday, May 30, 2003 3:49 PM
> Subject: Re: Fw: Help:FW Harddisk has no space!
>
>
> > Dear Stanley,
> >
> > yes, 'sync' only can ensure that all disk access
> is
> > finished. what I think may happen is the file
> table
> > not updated cause by this case. if the partition
> is
> > some kind of corrupt, you need to use 'fsck' to
> fix
> > the problem. Of course, you won't know fsck will
> > produce a positive or negative result
> > In the case of /home not have enough disk space, I
> > can't be sure that reboot will fix the problem. Of
> > course the OS will fix some of the filesystem
> error
> > during start up. (13MB data won't eat 200+MB
> space).
> > In the worst situation, you may need to restore
> the
> > whole system by tape.
> > As you know it is not a normal case, you may try
> > 'sync', 'fsck' or reboot. See which method can fix
> the
> > problem.
> >
> > Jackson
> >
> > --- Stanley Wong <stanley.wong at rexcapital.com.hk>
> > wrote:
> > > Jackson,
> > >
> > > I read the man of sync, which you mentioned. It
> > > shows it is only a program
> > > to "insure that all disk writes have been
> completed
> > > before the processor is
> > > halted in a way not suitably done by reboot(8) &
> > > halt(8)".Do u think it can
> > > recover the problem? And, do u think we just
> reboot
> > > the system and the
> > > problem will be fixed? Can you ensure the sytem
> can
> > > be running properly
> > > after the reboot even under the - amount of free
> > > space of partition /home?
> > >
> > > Regards,
> > > Stanley
> > >
> > > ----- Original Message -----
> > > From: "J Leung" <ckjleung at yahoo.com>
> > > To: "Stanley Wong"
> <stanley.wong at rexcapital.com.hk>
> > > Sent: Friday, May 30, 2003 9:53 AM
> > > Subject: Re: Fw: Help:FW Harddisk has no space!
> > >
> > >
> > > > Dear Stanley,
> > > >
> > > > 1) seems like those function is not available
> in
> > > your
> > > > Sidewinder, please man the function df and du,
> as
> > > you
> > > > know I don't have a sidewinder machine at the
> > > moment.
> > > > 2) you may notice that after running du, the
> /home
> > > > partition only have 13MB, I think it may cause
> by
> > > the
> > > > error report of file system.
> > > > 3) moreover, if this is the case of
> synchronize
> > > > between FAT and physical file system. Run the
> sync
> > > > command will correct the mismatch.
> > > >
> > > > Regards,
> > > > Jackson
> > > >
> > > >
> > > >
> > > > --- Stanley Wong
> <stanley.wong at rexcapital.com.hk>
> > > > wrote:
> > > > > Fm Stanley
> > > > > ----- Original Message -----
> > > > > From: "J Leung" <ckjleung at yahoo.com>
> > > > > To: "Stanley Wong"
> > > <stanley.wong at rexcapital.com.hk>
> > > > > Cc: <jacleung at asl.com.hk>
> > > > > Sent: Thursday, May 29, 2003 10:02 AM
> > > > > Subject: Re: Fw: Help:FW Harddisk has no
> space!
> > > > >
> > > > >
> > > > > > Dear Stanley,
> > > > > >
> > > > > > I'm not quite sure for this case, still
> trying
> > > to
> > > > > get
> > > > > > more information from SideWinder. You may
> try
> > > this
> > > > > in
> > > > > > the mean time.
> > > > > >
> > > > > > try this now to see the disk usage for
> /home
> > > (the
> > > > > last
> > > > > > statement:
> > > > > > df -h
> > > > > > du /home -h
> > > > > >
> > > > > > and send me the result.
> > > > > >
> > > > > > try this in lunch time period because it
> > > invoke
> > > > > sync
> > > > > > operation:
> > > > > >
> > > > > > df --sync -h
> > > > > >
> > > > > > Please send me the result afterward.
> > > > > >
> > > > > > Thanks and Regards,
> > > > > > Jackson
> > > > > > (ASL-HK)
> > > > > >
> > > > > >
> > > > > >
> > > > > > __________________________________
> > > > > > Do you Yahoo!?
> > > > > > Yahoo! Calendar - Free online calendar
> with
> > > sync
> > > > > to Outlook(TM).
> > > > > > http://calendar.yahoo.com> login: admin
> > > > > Password:
> > > > > Last login: Wed May 28 17:26:23 from
> 10.0.1.48
> > > > > Copyright 1992, 1993, 1994, 1995, 1996, 1997
> > > > > Berkeley Software Design, Inc.
> > > > > Copyright (c) 1980, 1983, 1986, 1988, 1990,
> > > 1991,
> > > > > 1993, 1994
> > > > > The Regents of the University of
> > > California.
> > > > > All rights reserved.
> > > > >
> > > > > SW_OPS Sun Nov 19 20:41:00 CST 2000
> > > > >
> > > > > Use of this software is governed by the BSDI
> End
> > > > > User Software License.
> > > > >
> > > > > If you do not accept the terms of this
> license,
> > > > > immediately return the
> > > > > distribution to the place of purchase for a
> full
> > > > > refund. Further
> > > > > use of the software will be considered to be
> > > > > acceptance of the terms
> > > > > of the license.
> > > > >
> > > > >
> > > > > You have new mail.
> > > > > intfw:User {1} % srole
> > > > > You have mail.
> > > > > intfw:Admn {1} % df
> > > > > Filesystem 1K-blocks Used Avail
> Capacity
> > > > > Mounted on
> > > > > /dev/sd0a 126959 18864 101747
> 16%
>
=== message truncated ===> intfw:User {1} % fsck
> /sbin/fsck: Operation not permitted.
> intfw:User {2} % srole
> You have mail.
> intfw:Admn {1} % fsck
> ** /dev/rsd0a (NO WRITE)
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 1630 files, 18864 used, 108095 free (79 frags, 13502
> blocks, 0.1% fragmentation)
> ** /dev/rsd0d (NO WRITE)
> ** Last Mounted on /home
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> UNREF FILE I=37770 OWNER=root MODE=100644
> SIZE=202235904 MTIME=May 30 16:15 2003
> CLEAR? no
>
> ** Phase 5 - Check Cyl groups
> 62 files, 211176 used, 87 free (87 frags, 0 blocks,
> 0.0% fragmentation)
> ** /dev/rsd0e (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 14152 files, 243973 used, 350954 free (546 frags,
> 43801 blocks, 0.1% fragmentation
> )
> ** /dev/rsd0f (NO WRITE)
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 4558 files, 75974 used, 974120 free (264 frags,
> 121732 blocks, 0.0% fragmentation)
> ** /dev/rsd0g (NO WRITE)
> ** Last Mounted on /var/spool
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 11 files, 538 used, 2592211 free (75 frags, 324017
> blocks, 0.0% fragmentation)
> ** /dev/rsd0h (NO WRITE)
> ** Last Mounted on /var/log
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> SUMMARY INFORMATION BAD
> SALVAGE? no
>
> BLK(S) MISSING IN BIT MAPS
> SALVAGE? no
>
> 1308 files, 1068378 used, 1945235 free (947 frags,
> 243036 blocks, 0.0% fragmentati
> on)
> intfw:Admn {2} % df
> Filesystem 1K-blocks Used Avail Capacity
> Mounted on
> /dev/sd0a 126959 18864 101747 16% /
> /dev/sd0d 211263 211176 -10477 105%
> /home
> /dev/sd0e 594927 243973 321207 43%
> /usr
> /dev/sd0f 1050094 75974 921615 8%
> /var
> /dev/sd0g 2592749 538 2462573 0%
> /var/spool
> /dev/sd0h 3013613 1068442 1794490 37%
> /var/log
> mfs:27 15855 2 15060 0%
> /tmp
> intfw:Admn {3} %
>
> intfw:Admn {9} % man fsck
> FSCK(8) BSD System Manager's
> Manual FSCK(8)
>
> NAME
> fsck - filesystem consistency check and
> interactive repair
>
> SYNOPSIS
> fsck -p [-f] [-m mode] [filesystem] ...
> fsck [-ny] [-b block#] [-c level] [-l
> maxparallel] [-m mode] [filesystem]
> ...
>
> DESCRIPTION
> The first form of fsck preens a standard set of
> filesystems or the speci-
> fied filesystems. It is normally used in the
> script /etc/rc during auto-
> matic reboot. Here fsck reads the table
> /etc/fstab to determine which
> filesystems to check. Only partitions in fstab
> that are mounted ``rw,''
> ``rq'' or ``ro'' and that have non-zero pass
> number are checked.
> Filesystems with pass number 1 (normally just
> the root filesystem) are
> checked one at a time. When pass 1 completes,
> all remaining filesystems
> are checked, running one process per disk
> drive. The disk drive contain-
> ing each filesystem is inferred from the
> longest prefix of the device
> name that ends in a digit; the remaining
> characters are assumed to be the
> partition designator. In preening mode,
> filesystems that are marked
> clean are skipped. Filesystems are marked
> clean when they are unmounted,
> when they have been mounted read-only, or when
> fsck runs on them success-
> fully.
>
> The kernel takes care that only a restricted
> class of innocuous filesys-
> tem inconsistencies can happen unless hardware
> or software failures in-
> tervene. These are limited to the following:
>
> Unreferenced inodes
> Link counts in inodes too large
> Missing blocks in the free map
> Blocks in the free map also in files
> Counts in the super-block wrong
>
> These are the only inconsistencies that fsck
> with the -p option will cor-
> rect; if it encounters other inconsistencies,
> it exits with an abnormal
> return status and an automatic reboot will then
> fail. For each corrected
> inconsistency one or more lines will be printed
> identifying the filesys-
> tem on which the correction will take place,
> and the nature of the cor-
> rection. After successfully correcting a
> filesystem, fsck will print the
> number of files on that filesystem, the number
> of used and free blocks,
> and the percentage of fragmentation.
>
> If sent a QUIT signal, fsck will finish the
> filesystem checks, then exit
> with an abnormal return status that causes an
> automatic reboot to fail.
> This is useful when you want to finish the
> filesystem checks during an
> automatic reboot, but do not want the machine
> to come up multiuser after
> the checks complete.
>
> Without the -p option, fsck audits and
> interactively repairs inconsistent
> conditions for filesystems. If the filesystem
> is inconsistent the opera-
> tor is prompted for concurrence before each
> correction is attempted. It
> should be noted that some of the corrective
> actions which are not cor-
> rectable under the -p option will result in
> some loss of data. The
> amount and severity of data lost may be
> determined from the diagnostic
> output. The default action for each
> consistency correction is to wait
> for the operator to respond yes or no. If the
> operator does not have
> write permission on the filesystem fsck will
> default to a -n action.
>
> Fsck has more consistency checks than its
> predecessors check, dcheck,
> fcheck, and icheck combined.
>
> The following flags are interpreted by fsck.
>
> -b Use the block specified immediately
> after the flag as the super
> block for the filesystem. Block 32 is
> usually an alternate super
> block.
>
=== message truncated ===
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
More information about the freebsd-questions
mailing list