From: Andrey Rahmatullin <wrar@altlinux.ru>
To: ALT Linux kernel packages development <devel-kernel@altlinux.ru>
Subject: Re: [d-kernel] Re: 2.4.23?
Date: Wed, 21 Jan 2004 12:05:54 +0500
Message-ID: <20040121070554.GA1659@wrars-comp.wrarsdomain> (raw)
In-Reply-To: <20040120185923.GA9261@lks.home>
[-- Attachment #1: Type: text/plain, Size: 3590 bytes --]
On Tue, Jan 20, 2004 at 09:59:23PM +0300, Konstantin A. Lepikhov wrote:
> вы все правильно сделали? Т.е. выполнили cdmrw -d /dev/hdc -f full, потом
> mkfs.ext2 /dev/hdc или mkudffs --media-type=cdrw -b 2048 /dev/hdc (если
> хотите udf)?
wrar@wrars-comp ~ $ ./cdmrw -d /dev/hdc -f full
not a mrw formatted disc
LBA space: DMA
wrar@wrars-comp ~ $ ./cdmrw -d /dev/hdc -p
mrw format running
LBA space: DMA
drive fails to support progress indicator
/dev/hdc: back ground format 0% complete
new media
progress: no progress indicator
progress: no progress indicator
progress: no progress indicator
wrar@wrars-comp ~ $ ./cdmrw -d /dev/hdc -p
disc is mrw formatted
LBA space: DMA
bgformat complete!
# mkfs.ext2 /dev/hdc
mke2fs 1.34 (25-Jul-2003)
Warning: could not erase sector 2: Attempt to write block from filesystem
resulted in short write
Filesystem label=
OS type: Linux
Block size=2048 (log=1)
Fragment size=2048 (log=1)
41568 inodes, 83136 blocks
4156 blocks (5.00%) reserved for the super user
First data block=0
6 block groups
16384 blocks per group, 16384 fragments per group
6928 inodes per group
Superblock backups stored on blocks:
16384, 49152, 81920
Warning: could not erase sector 0: Attempt to write block from
filesystem resulted in short write
mkfs.ext2: Attempt to write block from filesystem resulted in
short write while zeroing block 83104 at end of filesystem
Writing inode tables: 0/6
Could not write 8 blocks in inode table starting at 4: Attempt to
write block from filesystem resulted in short write
# e2fsck /dev/hdc
e2fsck 1.34 (25-Jul-2003)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/hdc
# e2fsck -b 16384 /dev/hdc
e2fsck 1.34 (25-Jul-2003)
e2fsck: Bad magic number in super-block while trying to open /dev/hdc
# mkudffs --media-type=cdrw -b 2048 /dev/hdc
start=0, blocks=16, type=RESERVED
start=16, blocks=3, type=VRS
start=19, blocks=237, type=USPACE
start=256, blocks=1, type=ANCHOR
start=257, blocks=31, type=USPACE
start=288, blocks=32, type=PVDS
start=320, blocks=32, type=LVID
start=352, blocks=32, type=STABLE
start=384, blocks=1024, type=SSPACE
start=1408, blocks=81440, type=PSPACE
start=82848, blocks=31, type=USPACE
start=82879, blocks=1, type=ANCHOR
start=82880, blocks=160, type=USPACE
start=83040, blocks=32, type=STABLE
start=83072, blocks=32, type=RVDS
start=83104, blocks=31, type=USPACE
start=83135, blocks=1, type=ANCHOR
# mount /dev/hdc -t udf /mnt/cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
и виснет на минуту. Потом
mount: wrong fs type, bad option, bad superblock on /dev/hdc,
or too many mounted file systems
В логах:
Jan 21 11:57:22 wrars-comp kernel: cdrom: mount opening for WRITE
Jan 21 11:57:22 wrars-comp kernel: cdrom: hdc: mrw address space DMA selected
Jan 21 11:57:22 wrars-comp kernel: cdrom open: mrw_status 'mrw complete'
Jan 21 11:57:22 wrars-comp kernel: UDF-fs DEBUG fs/udf/lowlevel.c:57:udf_get_last_session: XA disk: no,vol_desc_start=1560
Jan 21 11:57:22 wrars-comp kernel: UDF-fs DEBUG fs/udf/super.c:1544:udf_fill_super: Multi-session=0
Jan 21 11:57:22 wrars-comp kernel: UDF-fs DEBUG fs/udf/super.c:532:udf_vrs: Starting at sector 16 (2048 byte sectors)
Jan 21 11:58:23 wrars-comp kernel: attempt to access beyond end of device
Jan 21 11:58:23 wrars-comp kernel: hdc: rw=0, want=332548, limit=332544
Jan 21 11:58:23 wrars-comp kernel: UDF-fs: No VRS found
--
WBR, wRAR (ALT Linux Team)
Xft2 будет одной из заметных features наших новых дистрибутивов.
-- aen in devel@
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-21 7:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 11:34 [d-kernel] 2.4.23? Yury Aliaev
2004-01-12 12:41 ` Andrey Rahmatullin
2004-01-12 14:05 ` Ed V. Bartosh
2004-01-12 15:06 ` Andrey Rahmatullin
2004-01-12 15:16 ` Ed V. Bartosh
2004-01-12 15:40 ` Andrey Rahmatullin
2004-01-12 16:10 ` Anton Farygin
2004-01-12 16:56 ` [d-kernel] 2.4.23? Konstantin A. Lepikhov
2004-01-12 17:17 ` Anton Farygin
2004-01-13 7:54 ` Ed V. Bartosh
2004-01-13 8:06 ` Anton Farygin
2004-01-13 8:24 ` Alexey I. Froloff
2004-01-13 8:37 ` Ed V. Bartosh
2004-01-13 8:38 ` Anton Farygin
2004-01-13 8:19 ` Konstantin A. Lepikhov
2004-01-13 8:21 ` Anton Farygin
2004-01-13 8:40 ` Ed V. Bartosh
2004-01-13 8:48 ` Ed V. Bartosh
2004-01-13 9:05 ` Anton Farygin
2004-01-14 12:10 ` Michael Shigorin
2004-01-12 16:17 ` [d-kernel] 2.4.23? Ed V. Bartosh
2004-01-12 16:19 ` Michael Shigorin
2004-01-16 20:59 ` [d-kernel] 2.4.23? Konstantin A. Lepikhov
2004-01-17 6:08 ` Andrey Rahmatullin
2004-01-17 7:34 ` Konstantin A. Lepikhov
2004-01-17 8:18 ` Andrey Rahmatullin
2004-01-17 18:08 ` Konstantin A. Lepikhov
2004-01-17 18:35 ` Andrey Rahmatullin
2004-01-17 19:38 ` Konstantin A. Lepikhov
2004-01-18 6:57 ` Andrey Rahmatullin
2004-01-20 10:48 ` Andrey Rahmatullin
2004-01-20 16:45 ` Konstantin A. Lepikhov
2004-01-20 18:22 ` Andrey Rahmatullin
2004-01-20 18:59 ` Konstantin A. Lepikhov
2004-01-21 7:05 ` Andrey Rahmatullin [this message]
2004-01-19 16:26 ` Andrey Rahmatullin
2004-01-19 18:20 ` Konstantin A. Lepikhov
2004-01-12 15:50 ` [d-kernel] 2.4.23? Michael Shigorin
2004-01-12 15:54 ` Andrey Rahmatullin
2004-01-12 16:34 ` Michael Shigorin
2004-01-12 16:41 ` Alexander Bokovoy
2004-01-12 16:50 ` Michael Shigorin
2004-01-13 8:36 ` Yury Aliaev
2004-01-13 8:35 ` Yury Aliaev
2004-01-13 8:31 ` Yury Aliaev
2004-01-13 8:25 ` Yury Aliaev
2004-01-12 14:04 ` Ed V. Bartosh
2004-01-13 8:28 ` Yury Aliaev
2004-01-13 8:36 ` Anton Farygin
2004-01-13 10:04 ` Yury Aliaev
2004-01-13 10:20 ` Anton Farygin
2004-01-13 8:57 ` Ed V. Bartosh
2004-01-13 10:09 ` Yury Aliaev
2004-01-13 10:23 ` Anton Farygin
2004-01-13 11:09 ` Ed V. Bartosh
2004-01-13 11:12 ` Anton Farygin
2004-01-13 11:29 ` Ed V. Bartosh
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=20040121070554.GA1659@wrars-comp.wrarsdomain \
--to=wrar@altlinux.ru \
--cc=devel-kernel@altlinux.ru \
/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
ALT Linux kernel packages development
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel-kernel/0 devel-kernel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel-kernel devel-kernel/ http://lore.altlinux.org/devel-kernel \
devel-kernel@altlinux.org devel-kernel@altlinux.ru devel-kernel@altlinux.com
public-inbox-index devel-kernel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git