Linux-Hardware Digest #445, Volume #9            Tue, 16 Feb 99 21:13:33 EST

Contents:
  Clean Up lost+found (Jayasuthan)
  Re: Linux on PPC (Matteo Corti)
  Re: SONY AIT AUTOLOADER TSL-SA300C (Andreas Berger)
  Re: How to use Iomega Ditto (David Walsh)
  Re: Sound Blaster PCI 64 (Johannes Rest)
  Re: "uncompressing linux" takes 19 seconds !!! ("Clayton J. Ramseyer")
  Re: Has anyone REALLY done this before ??? (Gregory G. Woodbury)
  Re: SoundBlaster 16 SCSI II (Jose Urena)
  Printing with a DeskJet 722C (Greg Balls)
  Re: How to use Iomega Ditto ("David Z. Maze")
  Re: Linux and "Winprinters" (Dana A Levine)
  Linux and DiscOnChip 2000 (Morten Lund)
  Installing Linux on system with VIA chipset (Lisa Charles)
  Re: Linux Laptop news group ("David A. Frantz")
  Re: Same Disk RAID and Mirroring (Andy Glew)
  Re: Install - drive problems (Francis Devereux)
  Re: ATAPI Hack for Zip Drive Eject Button? (Francis Devereux)
  Re: S3 ViRGE /325 chipset
  Re: Ensoniq soundcard problem (Jose Urena)
  Re: Maximum Disk Size in 486 (Jose Urena)
  Re: Help needed re: Modem (Jose Urena)
  Re: Clean Up lost+found (Clifford Kite)

----------------------------------------------------------------------------

Date: Tue, 16 Feb 1999 15:34:53 -0800
From: Jayasuthan <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux.slackware,comp.os.linux.networking,ahn.tech.linux
Subject: Clean Up lost+found

Hi,

Lately I had a consider massive file corruption .. lucky that none
critical file corrupted. I could restore from backup but before that I
need some help. How can I clean up lost+found files.. < I don't want it
>. Two thos corrupted files ... how can I remove went "rm" doesn't works. The 
>corrupted file is in device format linux file under /dev/.

This problem cause under Kernel 2.2.0 ... hdparm -m8  is consider a
dangerous option. Please watchout !

Thank You,

Suthan

------------------------------

From: [EMAIL PROTECTED] (Matteo Corti)
Subject: Re: Linux on PPC
Date: 16 Feb 1999 08:27:22 +0100

On Mon, 15 Feb 1999 16:33:36 -0800, Clint Davis <[EMAIL PROTECTED]> wrote:
>I have a "spare"  Bull Estrella PPC.
>
>Is this a linux-able machine?  I have installed many
>Intel linux boxes but never a PPC.
>
>Clint

Take a look at www.linuxppc.org

        Matteo

------------------------------

From: Andreas Berger <[EMAIL PROTECTED]>
Subject: Re: SONY AIT AUTOLOADER TSL-SA300C
Date: Wed, 10 Feb 1999 10:47:24 +0100

Rakesh Jain wrote:
> 
> Hi there,
> 
>         Does anyone has the drivers for a sony AIT TSL-SA300C tape drive with
> autoloader running on linux. I have it on a dell 4300 system with redhat
> 5.2. I need to get the autoloader drivers. The mt stuff works fine but
> have not figured out a way to use the magazine with it.
> 
> Thanks
> rakesh
I saw a driver for "scsi changers". Search for it. May be that you have
the wrong kernel (the driver needs an older kernel). Perhaps you can
find a "user mode" driver using the scsi generic interface.

Andreas
-- 
Fifty-three percent of Fortune 1000 executives think the
Arch Deluxe is something that helps to run a computer.
-- Jericho Communications

------------------------------

From: David Walsh <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: How to use Iomega Ditto
Date: Tue, 16 Feb 1999 17:15:05 +1000

Read the ZIP-HOWTO

Juergen Fiedler wrote:

> Hi,
>
> I have to set up some backup solution. Urgently. The only piece of
> hardware in my possession that looks remotely usable for this task
> is an old Iomega Ditto Max. Now the question:
> How do I go about compiling support for it into the kernel?
> I heard that I need SCSI support. Then I also heard about compiling
> a ppa module. Which option (say, in 'make menuconfig') enables that?
> I have Slackware 3.6 with a 2.0.36 kernel. Seems it comes with ftape-2.08.
> Should I download a 4.x ftape? Can I unpack that into the Linux source tree
> or should I keep it separately? Can someone please tell me how to configure
> it?
> I'm really at a loss. I spent lots of time setting this Linux box up
>
> and I don't dare to play around with it too much before backing it up.
> Could some nice soul please help me out?
>
> TIA,
> Juergen


------------------------------

From: Johannes Rest <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,alt.os.linux
Subject: Re: Sound Blaster PCI 64
Date: Tue, 16 Feb 1999 09:04:54 +0100



Dana A Levine schrieb:
> 
> Graham Ashton wrote:
> 
> > In article <[EMAIL PROTECTED]>, Ray Hernandez wrote:
> >
> > >    I have a Sound Blaster PCI 64 sound card. I know it is really an
> > >Esoniq something or other, and I was wondering if anyone knows how to
> > >get it to work? Thankyou.
> > >p.s.-- I use RedHat 5.2
> >
> > have you tried the sndconfig utility that comes with red hat?
> >
> > --
> > Graham
> 
> There are two ways to do this. One is a little utility called OSS. You
> download a version for your kernel and run it and it enables sound. This
> utility, however, is commercial. The other thing that works (I just did
> this yesterday) is to get the newest kernel source (2.2.1) and build your
> own kernel. This release adds support for lots of new sound boards. Just
> configure it for your sound card and compile.
>                                     Hope this helps
>                                                                     -Dana

at home I've such a SB PCI 64. What options did you select? I've tried
several configs but none of them seem to work. I've tried to do a
insmod sb to insert sb.o (as suggested by one of the readme files)
but the resource is busy (I'm running kde and there's a sndserver
running)
Any idea?

Thanks
--
Johannes Rest, mailto: [EMAIL PROTECTED]                         
software design & management GmbH & Co. KG
Thomas-Dehler-Str. 27, D-81737 Muenchen, Germany
Tel.: +49 89 63812-438           Fax: +49 89 63812-444

------------------------------

From: "Clayton J. Ramseyer" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware,comp.os.linux.help,comp.os.linux.questions
Subject: Re: "uncompressing linux" takes 19 seconds !!!
Date: Tue, 16 Feb 1999 02:56:56 -0500
Reply-To: [EMAIL PROTECTED]

I would like to offer another possibility.
I have always installed Linux in multi HD situations with / and the swap
on the same physical drive.

Recently I attempted seperating the two between two different devices.
My system sped up dramatically though my BogoMIPS never changed.

The other issue is for a 486 your performance doesn't sound too bad to
me.

I have a Petium 150 and a rather small kernel and it take about as long
to uncompress it kernel image.

Good luck,
-- 
Clayton J. Ramseyer - CyberZard
[EMAIL PROTECTED] and/or [EMAIL PROTECTED] - ICQ# 2968751
"One of the worst performance of my career, and they never doubted it
for a
second." - Ferris Beuller's Day Off - Starring Matthew Broderick


------------------------------

From: [EMAIL PROTECTED] (Gregory G. Woodbury)
Subject: Re: Has anyone REALLY done this before ???
Date: 16 Feb 1999 08:20:17 GMT

Yin Tan Cui <[EMAIL PROTECTED]> shaped electrons to say:
>Hi.
>
>I have a compaq prosignia with an enbeded SCSI controller NCR53C710.
>I can not get this card working. My SCSI CD-ROM does not get detected,
>so are my hard disks.
>
>This is a card on EISA bus, however, this card is only supported on PCI
>bus. I have tried to compile different kernel to detect the card, but
>all of them failed. I tried most of the relavent images on the slackware
>bootdisk directory. non of them work. I'm losing my patient on this one.

  Having just read thru the Config.in script for SCSI devices, I can say
that support for NCR53c7,8xx devices are dependent on PCI support being
selected.

  On reading thru the 53c7,8xx.c driver code, it appears to me that the
driver says that the ncr53c710 *must* be a PCI device, and there is no
support for the device without having the PCI bios routines available.

  I would suspect that if the motherboard has PCI support, all the embedded
devices will be PCI by default. (Unless Compaq has really screwed things
up!)  Have you tried setting PCI and selecting 53c7,8xx?  If the controller
is embedded on the M/Board, I'd bet that it would work via PCI.

>I have been searching info on this for two weeks  now. people are saying
>that they have done it, and how easy it is. BUT NO ONE SAID EXACTLY HOW
>THEY DID IT. what driver they used for this card on EISA bus. I tried to
>contact these people by email, none of them replied. people say
>kernel-2.2.1 support this card on EISA bus. so I downloaded kernel-2.2.1
>and tried to compile it. BUT it seems to me the kernel still only
>support this card on PCI, not EISA. why do i say this. 'cause if I do
>not select "support for PCI BUS", then "support for ncr53c7,8xxx SCSI
>card" will be greyed out when I run make xconfig.

  Well, there could be a problem in xconfig. (Actually there are many
problems with xconfig.)  

  I do have one machine at work that has a 53c710 embedded controller, and
it works fine as long as I have the PCI support on.  (Actually, I can't turn
off PCI support!  Other devices in the system are in PCI slots.)

  If the motherboard has ANY PCI slots, you *need* to enable PCI so that the
kernel can properly initialize the empty slots. (Prevents false interrupts
and other weird things.)

  Seriously, go ahead and enable PCI and select the 53c7,8xx device, it
should work.
-- 
Gregory G. "Wolfe" Woodbury      `-_-'    Owner/Admin: wolves.durham.nc.us
ggw at wolves.durham.nc.us         U      Errant co-moderator of:
                                                  soc.religion.unitarian-univ
"The Line Eater is a boojum snark."     Hug your wolf.  (Thanks Peter.)

------------------------------

From: Jose Urena <[EMAIL PROTECTED]>
Subject: Re: SoundBlaster 16 SCSI II
Date: Tue, 02 Feb 1999 14:43:02 -0500


==============A977890EA8919A3EE12D62A2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

my old SB16 SCSI used to have a adaptec 1522 SCSI controller
the sound should be your normal Sb16

if you have any problems, read the jumper settings off the card
and use that info to configure the drivers

Notmyname wrote:

> Does anyone know how to install the driver for the SoundBlaster 16
> SCSI II in Redhat 5.2?
>
> Thanks in advance

==============A977890EA8919A3EE12D62A2
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
my old SB16 SCSI used to have a adaptec 1522 SCSI controller
<br>the sound should be your normal Sb16
<p>if you have any problems, read the jumper settings off the card
<br>and use that info to configure the drivers
<p>Notmyname wrote:
<blockquote TYPE=CITE>Does anyone know how to install the driver for the
SoundBlaster 16
<br>SCSI II in Redhat 5.2?
<p>Thanks in advance</blockquote>
</html>

==============A977890EA8919A3EE12D62A2==


------------------------------

From: Greg Balls <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Printing with a DeskJet 722C
Date: Tue, 16 Feb 1999 08:38:48 GMT

Last week I was printing just fine.

Then I got a cable modem.  It took me about half a day to get the
ethernet card working in Linux: I had to build a new kernel because my
old one didn't support the card.

Once I got that fixed, I fixed my isapnp.conf file, which had been
broken but never caused me any problems (everything worked, even though
the file wasn't read).

Then I downloaded, built, and installed KDE since I had a cable modem
and downloading stuff was no longer a problem.

Today I noticed that I can no longer print.  (I hadn't needed to print
anything for about a week.)

Any suggestions?

More details:
RH5.0 (kernel 2.0.31)
upgraded to kernel 2.0.36 with parallel printer support
I have the necessary linux software for the printer (pbm2ppa)

I feel like I've tried everything: I reinstalled the original kernel; I
broke my isapnp.conf file again; I moved the ethernet card to a
different slot; I took out the ethernet card completely; I even tried
debugging lp.c.

The only information produced by the lp module is
lp: Driver configured but no interfaces found.

The printer works fine under Windows95

Thanks,
Greg


------------------------------

From: "David Z. Maze" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: How to use Iomega Ditto
Date: 16 Feb 1999 10:50:36 -0500

Juergen Fiedler <[EMAIL PROTECTED]> writes:
JF> I have to set up some backup solution. Urgently. The only piece of
JF> hardware in my possession that looks remotely usable for this task
JF> is an old Iomega Ditto Max.

My advice if you need reliable backups is to ditch it and get
something else that actually works.

JF> How do I go about compiling support for it into the kernel?

You don't.

JF> I heard that I need SCSI support.

You don't.

JF> Then I also heard about compiling a ppa module.

You need this if you have an external (e.g. parallel port) drive.  If
you have an internal drive (probably connects to a Ditto Dash card),
you don't.

JF> I have Slackware 3.6 with a 2.0.36 kernel. Seems it comes with
JF> ftape-2.08.

If comes with ftape-3.04d, IIRC.

JF> Should I download a 4.x ftape?

Yes.  See http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/.

JF> Can I unpack that into the Linux source tree or should I keep it
JF> separately?

You should keep it separate.  It only builds as an external module
currently.

JF> Can someone please tell me how to configure it?

The README file does an adequate job.

-- 
David Maze             [EMAIL PROTECTED]          http://donut.mit.edu/dmaze/
"Hey, Doug, do you mind if I push the Emergency Booth Self-Destruct Button?"
"Oh, sure, Dave, whatever...you _do_ know what that does, right?"

------------------------------

From: Dana A Levine <[EMAIL PROTECTED]>
Subject: Re: Linux and "Winprinters"
Date: Tue, 16 Feb 1999 14:35:45 -0500

>how would you like a 'dumb' 3d card?  Why a modem?

Oh, like a Cyrix MediaGX. But that's a 'dumb' sound card too.


------------------------------

From: Morten Lund <[EMAIL PROTECTED]>
Subject: Linux and DiscOnChip 2000
Date: Tue, 16 Feb 1999 23:36:42 +0000

Hello

I just got a 386sx40Mhz Machine with 4 Megs of Ram, and a 8MB Disc...

I would like to install a small Linux on this machine... but what do I
need to compile into my kernel, to get support for this flash-disc? And
will it appear as a normal IDE-drive (/dev/hda1 for instance?)

The name of the disc is "DiscOnChip200"

Morten Lund....

PS Please reply to my email-adress!


------------------------------

From: Lisa Charles <[EMAIL PROTECTED]>
Subject: Installing Linux on system with VIA chipset
Date: Tue, 16 Feb 1999 22:17:36 GMT

Hello All
I just want to clarify. I am trying to install Linux on a system with an
EPOX MVP3C motherboard, with a VIA chip set and AWARD BIOS, using an AMD
K6-3D processor and IDE drives.
I have created the boot disks, but when I boot from it the devices are
not recognized. The primary drive on the primary channel is found but
the primary drive on the secondary channel ( cdrom) is not found. Come
to that, the ethernet card ( NE2000 clone ISA ) is also not found. I
also get some messages about unknown PCI devices but they scroll of the
screen so I am not sure what it says. Since my cdrom is not detected I
can not continue with the installation. I have also considered the
possibility of  trying to mount the cd on a windoze machine and sharing
it so that I can do an install with an SMB source, but my ethernet card
is not found. So for now I'm screwed it seems. Any help will be
appreciated
TIA
Thanks for the suggestion Trever but that won't help

William



------------------------------

From: "David A. Frantz" <[EMAIL PROTECTED]>
Subject: Re: Linux Laptop news group
Date: Tue, 16 Feb 1999 19:49:30 -0500

comp.os.linux.portable


matthew.r.pavlovich.1 wrote in message ...
>anyone know of one?
>
>



------------------------------

From: Andy Glew <[EMAIL PROTECTED]>
Crossposted-To: comp.arch,comp.arch.storage,alt.os.linux,comp.periphs
Subject: Re: Same Disk RAID and Mirroring
Date: Tue, 16 Feb 1999 16:44:15 -0600

While a compile runs, some minor notes about error distributions
and their relavance to "Single Disk RAID":

If surface errors are typically limited to a small number of contiguous
blocks - e.g. 1 block, 2 blocks, 4 blocks, etc. - then placing the parity
block on the same track as the data block, perhaps with interleaving,
is viable.  The more interleaving required (beyond the interleaving that
is best for ordinary performance - which I think is usually no interleaving
these days), the worse.

Interleaving could be taken in two directions - either logically
contiguous data blocks could be separated from each other
so as to minimize the chance of an error hitting them both,
or logically contiguous data blocks could be made physically contiguous,
but belong to different parity groups - increasing overhead for
small multiple block writes, but not affecting the limit cases of single
block or large multiple block writes.


However, I think it is more likely that surface errors are denominated
not in terms of "blocks", but in terms of either distance or time.

In particular, time may be the real culprit: if the disk head gets hot after
colliding with an asperity, it may not read reliably for the timespan
necessary for it to cool down.  (I was somewhat amazed to learn that
head/disk collisions are commonplace now, and that polishing by the
disk head of the surface is depended on; when I started in this
field, head crashes had a literal meaning.)

Similarly, mechanical vibrations, etc.

The big problem with such time denominated errors - not really
surface errors, but errors associated with the head physics - is
that, as RPM goes up, the amount of interleaving that would be
required to correct such errors using parity blocks goes up dramatically.
The more interleaving, the worse the performance of single disk RAID
with parity blocks in the same track as the data blocks.


---

Somebody asked me what this would give beyond the ECC codes
already used by disk drive vendors.

Correct me if I am wrong (but make sure your math is good :-) )
but disk block ECC codes are only able to correct errors that occur
within a disk block.  They cannot correct errors that last longer than
a single disk block - i.e. the bits are not spatially spread out over more
than a sector.

So, again, it comes down to the distribution of errors: if error bursts
are a fraction of a disk block, ECC codes will be good.  If error bursts
are larger than this, but less than a small number of disk blocks,
error correction across multiple disk blocks in the same track would be good.
If error bursts are large multiples of the disk block in size, something
else needs to be done.


------------------------------

From: Francis Devereux <[EMAIL PROTECTED]>
Subject: Re: Install - drive problems
Date: Wed, 17 Feb 1999 00:39:24 GMT

try creating a small DOS or windows partition on hdb using windows
fdisk before you create your linux partitions or boot linux.  If you
already have any linux partitions on hdb from previous install
attempts then delete them all first.  Linux will then see the DOS
partition and work out the geometry from it.

Francis

P.S i am not sure if this will work but it helped me in a similar
situation so it's probably worth a try.


------------------------------

From: Francis Devereux <[EMAIL PROTECTED]>
Subject: Re: ATAPI Hack for Zip Drive Eject Button?
Date: Wed, 17 Feb 1999 00:28:59 GMT

I get the impression from your post that you are using the IDE-SCSI
emualtion to access your zip drive.  Maybe this is what is causing
your problems.  I use the IDE/ATAPI FLOPPY support to access my ATAPI
zip drive and the eject button works fine (it is only disabled when I
have a zip disk mounted).

Francis.


------------------------------

From: [EMAIL PROTECTED] ()
Crossposted-To: comp.os.linux.questions
Subject: Re: S3 ViRGE /325 chipset
Reply-To: [EMAIL PROTECTED]
Date: Wed, 17 Feb 1999 01:49:03 GMT

On Tue, 16 Feb 1999 12:38:39 -0600, Glendon Shaw wrote:
>I have been having X problems with my S3 ViRGE 325 video card. It works for
>a wile and then causes a severe crash. I have to cold boot. I am using the
>S3 server and the virge adapter.

I'm using the same chipset, but am using XFree86 3.3.3.1 with the SVGA
server. Seems to perform a little bit better, and support the Virge a
bit better. You might also want to check out the S3V server, instead
of the plain S3.

--
-- Doug --
  In a mature society, "civil servant" is semantically equal
  to "civil master".
  -- Lazarus Long

------------------------------

From: Jose Urena <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.questions,linux.redhat.misc
Subject: Re: Ensoniq soundcard problem
Date: Tue, 16 Feb 1999 10:04:13 -0500

Mark Smith wrote:

>
> However, I'm going for 2.2 tonight because I want to see what the fuss is
> about anyhow.  And, I'm getting another system in the next couple of weeks
> too so I'm sure I'll get a newer and more supported card.
>

the Newer the Hardware, the less likely it is supported.
Take you time and used tested hardware, it will save you money and aggravation


------------------------------

From: Jose Urena <[EMAIL PROTECTED]>
Subject: Re: Maximum Disk Size in 486
Date: Tue, 16 Feb 1999 10:07:46 -0500

you will probably have to use the append="hda=c,h,s" option in lilo.conf
the Bios is only used to boot The kernel, after the kernel is loaded, it usually
does not rely on the bios anymore

Charles Sullivan wrote:

> It's not clear to me that the processor has much to do with it; it's more
> the IDE
> adapter.  Linux can deal with more than the 1024 cylinder limit imposed by
> the standard DOS BIOS call (INT 13h) because it doesn't use the BIOS,
> but you'll have to specifically tell the kernel (and fdisk) the drive
> geometry.
>
> kernel versions prior to v2.2.0 (RH5.2 ships with v2.0.36) have a
> (non-fatal)
> problem with LBA geometry, but your older? BIOS  probably doesn't support
> LBA anyway.   If you intend to devote your entire drive to Linux,  you
> needn't care;
> your only concern will be to keep the kernel resident entirely below the
> 1024
> cylinder boundary if you expect to boot from the hard drive with LILO.
>
> Regards,
> Charles Sullivan
>
> [EMAIL PROTECTED] wrote in message <7a5ip1$ito$[EMAIL PROTECTED]>...
> >I am currently running redhat 5.2 on a 500 meg drive in a 486. I would like
> >more disk space but am not sure what my options are. I believe that the 486
> >architecture does not recognize drives larger than 500 or so megs under
> dos. I
> >am not sure what to expect or if it is advisable to just pop in a new
> gigabyte
> >plus drive. If someone could be kind enough to drop me a quick note i'd
> >appreciate it. TIA.
> >
> >-----------== Posted via Deja News, The Discussion Network ==----------
> >http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own


------------------------------

From: Jose Urena <[EMAIL PROTECTED]>
Subject: Re: Help needed re: Modem
Date: Tue, 16 Feb 1999 10:11:51 -0500

from MS, goto the control panel, modem, diagnostics, pick you modem, and
click more info

if around the Rockwell name you see HCF, you have a software modem

Howard Close wrote:

> At about the time I discovered the wonders(?) of Linux and
> repartitioned my disk to take both Win/MS and Linux, my old
> 28.8 modem expired and I bought what was described as a
> "Rockwell 56k Modem". It has worked exceptionally well with
> Windoze. As I began to become more acquainted with Linux I
> naturally wanted to access the net via my new OS and become
> less reliant on BillG and began to wade my way through the
> swamp that is lovingly called pppd. After months of trying I
> have failed to connect and despite help from D. Richard Hipp,
> the author of "Eznet" (highly recommended to those equally
> struggling in the swamp - see   http://www.hwaci.com/drh/ )
> which has been much appreciated I am still drowning. The idea
> has come to me that this modem is what I have heard described
> as a "Winmodem" i.e. it requires the dreaded MS OS to be
> present to work..
> Can anyone to tell me what tests I can run to test this
> hypothesis ? I thank you all for your help past and present.
> It is wonderful to be a member of this community.
>
> Howard Close
>
> --
> "We may see the small value God has for riches by the people
> he gives them to"  Alexander Pope


------------------------------

From: [EMAIL PROTECTED] (Clifford Kite)
Crossposted-To: alt.os.linux.slackware,comp.os.linux.networking,ahn.tech.linux
Subject: Re: Clean Up lost+found
Date: 16 Feb 1999 08:33:49 -0600

Jayasuthan ([EMAIL PROTECTED]) wrote:
: Hi,

: Lately I had a consider massive file corruption .. lucky that none
: critical file corrupted. I could restore from backup but before that I
: need some help. How can I clean up lost+found files.. < I don't want it
: >. Two thos corrupted files ... how can I remove went "rm" doesn't works. The 
:corrupted file is in device format linux file under /dev/.

Here is an old post on this subject.  I haven't had an occasion to use
the technique described and disclaim any responsibility for whatever
happens when you use it.

---
Subject: Re: Removing files from /lost+found

>
>These will be corrupt, immuable, device inodes.  You can only get rid
>of them with a low-level filesystem editor (see previous posts on the
>topic) as chattr does not work on device inodes for non-existant
>devices.

The only way to really clear these is to boot up single user
mode with the disk unmounted (or mounted read-only if it's the
root filesystem). Make a list of the file (The #nnnn number is
the inode number, you can confirm this by doing ls -i) inodes
into a file. Edit the file so that it's a list of commands like

    clri <inode-number>

With with <inode-number> replaced by the inode number of
the file, of course. You can do this by...

    cd /lost+found ; ls -i | awk '{print $1}' | sed -e '1,$ s/^/clri /'
>script_file

Then run debugfs with the -w and -f option to clear the inodes.
When debugfs exits, run a full e2fsck. This should detect the now
unreferenced files from lost+found and remove them.

    debugfs -w -f script_file
    e2fsck -fvy /dev/...

I had a machine once that use to mangle the news spool once a
week (turned out to be memory problems). Anyway this proceedure
became second nature.

Oh yeah, almost forgot the disclaimer. What you are about to do
is serious black magic so anything you trash is your own
responsibly. :) Make sure to read up the man pages first.


: This problem cause under Kernel 2.2.0 ... hdparm -m8  is consider a
: dangerous option. Please watchout !

--
Clifford Kite <[EMAIL PROTECTED]>                       Not a guru. (tm)
/* Microsoft is a great marketing organization.
 * It _has_ to be */

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.hardware) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Hardware Digest
******************************

Reply via email to