From: Heinz Diehl <hd@cavy.de>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: Warning, 2.5.3 eats filesystems
Date: Fri, 8 Feb 2002 22:48:38 +0100 [thread overview]
Message-ID: <20020208214838.GA1129@chiara.cavy.de> (raw)
In-Reply-To: <20020206233051.GA503@chiara.cavy.de> <Pine.GSO.4.21.0202061836450.22680-100000@weyl.math.psu.edu> <20020208105050.GA175@elf.ucw.cz>
In-Reply-To: <20020208105050.GA175@elf.ucw.cz>
On Fri Feb 08 2002, Pavel Machek wrote:
> For me, mounted filesystems look like this:
[....]
Yep. I sent the "mount" output already to Alexander Viro, unfortunately I
did not Cc: the mail to lkml.
/dev/hda1 on / type ext2 (rw)
proc on /proc type proc (rw)
/dev/hda6 on /usr type ext2 (rw)
/dev/hda5 on /home type ext2 (rw)
/dev/hdb5 on /var/spool/news type ext2 (rw)
tmpfs on /dev/shm type shm (rw)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /var/tmp type tmpfs (rw)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev06)
(prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at e000 [size=16]
[....]
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c586b (rev 41) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
hda: IBM-DHEA-36481, ATA DISK drive
hdb: Conner Peripherals 1275MB - CFS1275A, ATA DISK drive
hdc: CD-540E, ATAPI CD/DVD-ROM drive
hdd: CD-W54E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 12692736 sectors (6499 MB) w/472KiB Cache, CHS=790/255/63, UDMA(33)
hdb: 2496876 sectors (1278 MB) w/64KiB Cache, CHS=2477/16/63, DMA
[....]
chiara:~ # hdparm /dev/hda /dev/hdb
/dev/hda:
multcount = 16 (on)
I/O support = 3 (32-bit w/sync)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 790/255/63, sectors = 12692736, start = 0
/dev/hdb:
multcount = 8 (on)
I/O support = 3 (32-bit w/sync)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 619/64/63, sectors = 2496876, start = 0
--
# Heinz Diehl, 68259 Mannheim, Germany
next prev parent reply other threads:[~2002-02-08 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 19:28 Warning, 2.5.3 eats filesystems Pavel Machek
2002-02-05 23:14 ` Daniel Pittman
2002-02-06 0:59 ` Skip Ford
2002-02-06 1:39 ` Dave Jones
2002-02-06 4:59 ` Daniel Pittman
2002-02-06 15:42 ` Pavel Machek
2002-02-06 23:30 ` Heinz Diehl
2002-02-06 23:39 ` Alexander Viro
2002-02-07 20:34 ` Heinz Diehl
2002-02-08 10:50 ` Pavel Machek
2002-02-08 21:48 ` Heinz Diehl [this message]
2002-02-08 11:14 ` Pavel Machek
2002-02-08 21:50 ` Andre Hedrick
2002-02-08 11:36 ` WARNING: 2.5.3 -- IDE damages data! [was Re: Warning, 2.5.3 eats filesystems] Pavel Machek
2002-02-06 17:49 ` Warning, 2.5.3 eats filesystems Olaf Zaplinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020208214838.GA1129@chiara.cavy.de \
--to=hd@cavy.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox