From: Nick Burrett <nick@dsvr.net>
To: reiserfs-list@namesys.com
Subject: symlink has wrong sd_blocks count
Date: Tue, 18 Feb 2003 10:53:25 +0000 [thread overview]
Message-ID: <3E5210A5.1030108@dsvr.net> (raw)
I'm running a stock 2.4.20 kernel with the reiserfs quota patches applied.
Simply creating a symlink and then running reiserfsck shows errors like
this:
/foofile 2 4 has wrong sd_blocks 8, has to be 1
I've reproduced this 100% on 100 filesystems on two servers.
bash-2.05# lvcreate -L 100M -n test vol01
lvcreate -- doing automatic backup of "vol01"
lvcreate -- logical volume "/dev/vol01/test" successfully created
bash-2.05# mkreiserfs /dev/vol01/test
<-------------mkreiserfs, 2002------------->
reiserfsprogs 3.6.2
mkreiserfs: Guessing about desired format..
mkreiserfs: Kernel 2.4.20 is running.
Format 3.6 with standard journal
Count of blocks on the device: 25600
Number of blocks consumed by mkreiserfs formatting process: 8212
Blocksize: 4096
Hash function used to sort names: "r5"
Journal Size 8193 blocks (first block 18)
Journal Max transaction length 1024
inode generation number: 0
UUID: cae72cae-5469-4e60-9b7f-7ffd662c3967
ATTENTION: YOU SHOULD REBOOT AFTER FDISK!
ALL DATA WILL BE LOST ON '/dev/vol01/test'!
Continue (y/n):y
Initializing journal - 0%....20%....40%....60%....80%....100%
Syncing..ok
[...snipped...]
bash-2.05# reiserfsck --check /dev/vol01/test
<-------------reiserfsck, 2002------------->
reiserfsprogs 3.6.2
Will read-only check consistency of the filesystem on /dev/vol01/test
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --check started at Tue Feb 18 10:47:22 2003
###########
Replaying journal..
No transactions found
Checking S+tree..ok
Comparing bitmaps..ok
Checking Semantic tree...
ok
No corruptions found
There are on the filesystem:
Leaves 1
Internal nodes 0
Directories 1
Other files 0
Data block pointers 0 (0 of them are zero)
Safe links 0
###########
reiserfsck finished at Tue Feb 18 10:47:22 2003
###########
bash-2.05# mount /dev/vol01/test /mnt
bash-2.05# cd /mnt
bash-2.05# touch bar
bash-2.05# ln -s bar foo
bash-2.05# cd /
bash-2.05# umount /mnt
bash-2.05# reiserfsck --check /dev/vol01/test
<-------------reiserfsck, 2002------------->
reiserfsprogs 3.6.2
Will read-only check consistency of the filesystem on /dev/vol01/test
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --check started at Tue Feb 18 10:48:04 2003
###########
Replaying journal..
No transactions found
Checking S+tree..ok
Comparing bitmaps..ok
Checking Semantic tree...
/foofile 2 4 has wrong sd_blocks 8, has to be 1
ok
There were found 1 corruptions which can be fixed with --fix-fixable
###########
reiserfsck finished at Tue Feb 18 10:48:04 2003
###########
bash-2.05#
--
Nick Burrett
Network Engineer, Designer Servers Ltd. http://www.dsvr.co.uk
next reply other threads:[~2003-02-18 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 10:53 Nick Burrett [this message]
2003-02-18 11:42 ` symlink has wrong sd_blocks count Oleg Drokin
2003-02-18 12:56 ` Chris Mason
2003-02-18 13:37 ` Oleg Drokin
2003-02-18 13:41 ` Chris Mason
2003-02-18 13:43 ` Oleg Drokin
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=3E5210A5.1030108@dsvr.net \
--to=nick@dsvr.net \
--cc=reiserfs-list@namesys.com \
/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.