From: Thomas Steudten <alpha@steudten.com>
To: fluca1978@virgilio.it
Cc: linux-admin@vger.kernel.org
Subject: Re: attempt to access beyond end of device
Date: Tue, 13 Apr 2004 14:44:12 +0200 [thread overview]
Message-ID: <407BE09C.3000302@steudten.com> (raw)
In-Reply-To: <200404131345.54605.fluca1978@virgilio.it>
Humm, is it possible, that the device was a floppy?
ls -l /dev/fd0* or cat /proc/devices show you, that
the block device 2:0 is the floppy device.
Check this first.
>>Try fsck.ext2 (or fsck) with -fvn <your root device eg /dev/hda1>.
>>-n tests in read-only mode.
>>
>
>
> Ok, here there's the result:
>
> fsck 1.27 (8-Mar-2002)
> e2fsck 1.27 (8-Mar-2002)
> Warning! /dev/hda1 is mounted.
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
>
> 30 inodes used (1%)
> 1 non-contiguous inodes (3.3%)
> # of inodes with ind/dind/tind blocks: 10/6/0
> 6937 blocks used (86%)
> 0 bad blocks
> 0 large files
>
> 18 regular files
> 2 directories
> 0 character device files
> 0 block device files
> 0 fifos
> 0 links
> 1 symbolic links (1 fast symbolic links)
> 0 sockets
> --------
> 21 files
>
> it seems correct, isn't it? I've tried also to dd to /dev/null and it worked
> well:
> 16002+0 records in
> 16002+0 records out
> 8193024 bytes transferred in 0.454885 seconds (18011202 bytes/sec)
>
> any idea?
> Thanks,
> Luca
>
>
>
--
Tom
LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?
next prev parent reply other threads:[~2004-04-13 12:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 10:03 attempt to access beyond end of device Luca Ferrari
2004-04-13 10:41 ` Thomas Steudten
2004-04-13 11:08 ` Luca Ferrari
2004-04-13 11:20 ` Thomas Steudten
2004-04-13 11:45 ` Luca Ferrari
2004-04-13 12:44 ` Thomas Steudten [this message]
2004-04-13 12:53 ` Luca Ferrari
-- strict thread matches above, loose matches on Subject: below --
2014-03-24 7:13 Piotr Szymaniak
2014-03-24 7:37 ` Vyacheslav Dubeyko
2014-03-24 20:49 ` Piotr Szymaniak
2014-03-25 9:18 ` Vyacheslav Dubeyko
2014-03-27 12:39 ` Piotr Szymaniak
2014-03-29 14:49 ` Vyacheslav Dubeyko
2014-03-24 22:31 ` Piotr Szymaniak
2010-04-26 20:20 Re: Attempt to Access Beyond End of Device willis
2010-04-26 20:54 ` Eric Sandeen
2007-09-10 13:59 Federico Sevilla III
2007-09-10 14:44 ` Justin Piszcz
2007-09-10 14:59 ` Federico Sevilla III
2007-09-10 15:45 ` Justin Piszcz
2007-09-10 15:51 ` Federico Sevilla III
2007-09-10 15:47 ` Eric Sandeen
2007-09-10 15:54 ` Federico Sevilla III
2007-09-10 16:28 ` Eric Sandeen
[not found] ` <cc7060690709111208u3e0842f9rd6edff16539b8a28@mail.gmail.com>
2007-09-12 5:17 ` Federico Sevilla III
2006-12-05 14:01 attempt to access beyond end of device Koen Vereeken
2006-01-19 12:02 Handling of read errors in raid6 Filipe Maia
2006-01-19 20:39 ` attempt to access beyond end of device PFC
2002-12-06 5:21 Justin Pryzby
2002-12-05 18:54 Justin Pryzby
2000-12-07 15:56 Jan Niehusmann
2000-12-07 16:34 ` Andries Brouwer
2000-12-07 17:10 ` John Kennedy
2000-11-24 9:02 Janek
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=407BE09C.3000302@steudten.com \
--to=alpha@steudten.com \
--cc=fluca1978@virgilio.it \
--cc=linux-admin@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.