FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Laptop

LinkBack Thread Tools
Old 01-15-2008, 07:11 PM
Michelle Konzack
Default fsck problem

Hello *,

I have an Aspire 1350Lmi with a 60 GByte Travelstar:

Disk Drive: /dev/hda
Size: 60011642880 bytes, 60.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 7296

Name Flags Part Type FS Type [Label] Size (MB)
hda1 Boot Primary Linux ext3 [Rescue_root] 1003,49
hda2 Primary Linux swap / Solaris 1003,49
hda3 Primary Linux ext3 [Temp] 5996,23
hda5 Logical Linux ext3 [Production_root] 3002,23
hda6 Logical Linux ext3 [Production_var] 501,75
hda7 Logical Linux ext3 [Production_couri] 501,75
hda8 Logical Linux ext3 [Production_pgsql] 5000,98
hda9 Logical Linux ext3 [Production_maild] 5000,98
hda10 Logical Linux ext3 [Production_home] 38000,80

and while mountig /dev/hda10 it has locked the entired Laptop...

[root@aspire1350.private:~/] fsck.ext3 -c /dev/hda10
e2fsck 1.37 (21-Mar-2005)
/dev/hda10: stelle das Journal wieder her
Suche nach defekten Blöcken (Nur-Lesen-Modus):erledigt 29
ext2fs_update_bb_inode: Could not allocate block in ext2 filesystem beim Updaten
des 'Bad Block'-Inodes

Now I was running the last "2 days 8 hours 25 minutes 53 seconds" the
following command (on an USB-IDE/SATA adapter):

[root@tp570.private:/] LC_ALL=C fsck.ext3 -v -f -c -c -k -t /dev/sda10
e2fsck 1.37 (21-Mar-2005)
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: done 529
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Peak memory: Memory used: 226k/8360k (61k/165k), time: 203153.69/25.62/20.50
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda10: ***** FILE SYSTEM WAS MODIFIED *****

185452 inodes used (3%)
2217 non-contiguous inodes (1.2%)
# of inodes with ind/dind/tind blocks: 43219/1245/0
8149185 blocks used (87%)
0 bad blocks
0 large files

160329 regular files
23760 directories
1 character device file
0 block device files
1 fifo
0 links
1352 symbolic links (297 fast symbolic links)
0 sockets
185443 files
Memory used: 190k/0k (5k/186k), time: 203156.86/28.07/20.61

but while mounting and transfering gigabyted of Debian packages to a
local mirror /dev/sda10 or /dev/hda10 lost its ext3 journal again...

How to solv this problem?

I have arround 32 GByte data on the partition...

Thanks, Greetings and nice Day
Michelle Konzack
Tamay Dogan Network

Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSN LinuxMichi
0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Old 01-16-2008, 01:12 PM
Default fsck problem

On Tue, Jan 15, 2008 at 09:11:35PM +0100, Michelle Konzack wrote:
> hda10 Logical Linux ext3 [Production_home] 38000,80

> e2fsck 1.37 (21-Mar-2005)

too old - try to backport newer e2fsprogs from stable/testing.


To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Old 01-16-2008, 03:31 PM
Default fsck problem

Michelle Konzack wrote:
> and while mountig /dev/hda10 it has locked the entired Laptop...
> ...
> [root@aspire1350.private:~/] fsck.ext3 -c /dev/hda10
> Checking for bad blocks (non-destructive read-write test)
> 0 bad blocks

Since you have zero bad blocks you might consider not using the -c
option to run the badblocks program. I have always assumed that this
would avoid a lot of machine resources if it is not needed. Not sure
if this is related to your issue or not.

> but while mounting and transfering gigabyted of Debian packages to a
> local mirror /dev/sda10 or /dev/hda10 lost its ext3 journal again...

I am not sure what "lost its ext3 journal" means in detail. How are
you observing and determining that?

Between booting and mounting and copying are you hibernating or
sleeping the machine?

> How to solv this problem?

This is not laptop specific and so if you don't find a satisfactory
answer here you might consider posting to the larger debian-user
audience. There would be a larger pool of knowledge to draw from
there. This looks to be specifically an ext3 issue. But many people
do very similar things every day and don't see this problem and so the
difficulty will be to determine why your installation is somehow


Thread Tools

All times are GMT. The time now is 03:52 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org