From: Alex Yustasov <snmon@server.by>
To: Maxim Tyurin <community@altlinux.ru>
Subject: Re: [Comm] Re[2]: [Comm] Сломалась flash-ка
Date: Fri, 4 Apr 2003 13:04:15 +0300
Message-ID: <20030404100415.GA9452@server.by> (raw)
In-Reply-To: <20030403173100.GH10895@mrkooll.tdr.pibhe.com>
On Thu, Apr 03, 2003 at 08:31:00PM +0300, Maxim Tyurin wrote:
> А вылетит флешка - другую из шкафа достану :)
На рассаду флешек не дадите? :)
Проверил флешку на bad blocki
mke2fs -c -c /dev/sda1
Выдала список плохих блоков, среди них 57345, 73729.
Сделал список bad-ов в файл (каждый bad на одной строчке).
Делаю mke2fs -l bad-blocks /dev/sda1. Результат внизу.
Superblock backups получаются именно в эти блоки.
Потом ломается по прежнему. Bad блоки всетаки используются?
Или я что-то не так делаю?
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
32000 inodes, 127975 blocks
6398 blocks (5.00%) reserved for the super user
First data block=1
16 block groups
8192 blocks per group, 8192 fragments per group
2000 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729
Warning: the backup superblock/group descriptors at block 49153 contain
bad blocks.
Warning: the backup superblock/group descriptors at block 57345 contain
bad blocks.
Warning: the backup superblock/group descriptors at block 73729 contain
bad blocks.
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
next prev parent reply other threads:[~2003-04-04 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 11:13 Alex Yustasov
2003-04-02 12:44 ` Oleg K. Artemjev
2003-04-02 13:26 ` Alex Yustasov
2003-04-03 3:33 ` Alex Yustasov
2003-04-03 5:03 ` Dmitry Lebkov
2003-04-03 6:42 ` Maxim Tyurin
2003-04-03 16:20 ` [Comm] Re[2]: " ASA
2003-04-03 17:31 ` Maxim Tyurin
2003-04-04 10:04 ` Alex Yustasov [this message]
2003-04-02 13:44 ` Artem Pastukhov
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=20030404100415.GA9452@server.by \
--to=snmon@server.by \
--cc=community@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 Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/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 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git