program12 | 29 May 02:44 2016

Hello

Hi,
I am Kristi and i saw your contact through google page of your country which impress me and i feel we can be
friends to share ideals and reason together for good,if not bad then let us know more about each other and i
hope there will be no problem for us to be friend with no bad intention.You can also reply me through
email(cplkristibakar <at> outlook.com) so that i can share details about myself, i will be waiting to hear
from you soon. 
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Arnd Bergmann | 27 May 22:22 2016
Picon
Gravatar

[PATCH] reiserfs: avoid uninitialized variable use

I got this warning on an ARM64 allmodconfig build with gcc-5.3:

fs/reiserfs/ibalance.c: In function 'balance_internal':
fs/reiserfs/ibalance.c:1158:3: error: 'new_insert_key' may be used uninitialized in this function [-Werror=maybe-uninitialized]
   memcpy(new_insert_key_addr, &new_insert_key, KEY_SIZE);

The warning is correct, in fact both new_insert_key and new_insert_ptr
are only updated inside of an if() block, but used at the end of
the function.

Looking at how the balance_internal() function gets called, it
is clear that this is harmless because the caller never uses the
updated arrays, they are initialized from balance_leaf_new_nodes()
and then passed into balance_internal().

This has not changed at all since the start of the git history,
but apparently the warning has only recently appeared.

This modifies the function to only update the two argument variables
when the new_insert_key and new_insert_ptr have been updated, to
get rid of the warning.

Signed-off-by: Arnd Bergmann <arnd <at> arndb.de>
---
I thought I had send this on May 12 when I first became aware of
the warning, but I can't find a reference to that now on any
mailing list archives, and I'm not sure who is picking up
reiserfs patches these days.

The warning is now one of the few 'allmodconfig' warnings for
(Continue reading)

Dušan Čolić | 27 May 11:16 2016
Picon

[Bug]Reiser4-for-4.5.3 mount: page allocation failure

I recieved this error few days ago.
Remounting this partition doesn't reproduce the error as it's
automatically fscked.

Thanks

Dusan

Mount options:
/dev/md125        /mnt/backup    reiser4
noatime,noauto,onerror=remount-ro  0 0

May 25 03:29:57 krshina3 kernel: reiser4: md125: found disk format 4.0.1.
May 25 03:29:57 krshina3 kernel: mount: page allocation failure:
order:4, mode:0x26040c0
May 25 03:29:57 krshina3 kernel: CPU: 2 PID: 7876 Comm: mount Not
tainted 4.5.3-gentoo #4
May 25 03:29:57 krshina3 kernel: Hardware name: Gigabyte Technology
Co., Ltd. To be filled by O.E.M./B75-D3V, BIOS F5 07/04/2012
May 25 03:29:57 krshina3 kernel:  0000000000000006 ffffffff81219767
0000000000000001 ffff8801bfe5bb30
May 25 03:29:57 krshina3 kernel:  ffffffff810d2ded ffffffff8192ed30
ffff88022e315168 026240c000000010
May 25 03:29:57 krshina3 kernel:  0000000000000000 fffffffffffffff0
0000000000000001 ffffffff8192ed00
May 25 03:29:57 krshina3 kernel: Call Trace:
May 25 03:29:57 krshina3 kernel:  [<ffffffff81219767>] ? dump_stack+0x46/0x59
May 25 03:29:57 krshina3 kernel:  [<ffffffff810d2ded>] ?
warn_alloc_failed+0x113/0x12b
May 25 03:29:57 krshina3 kernel:  [<ffffffff810d5222>] ?
(Continue reading)

doiggl | 27 May 12:09 2016
Picon

Is there some code [to run on Linux r4 enabled kernel] to extract a list of file-names from the reiser4 meta-data ?

Hello,
Is there some code [to run on Linux r4 enabled kernel] to extract a list
of file-names from the reiser4 meta-data ?
Thanks
--Glenn

meta data 

# ll
total 48362807
-rw-r--r-- 1 root users 24,733,058,856 Apr 14 04:24 r4meta-sdb

packed     # debugfs.reiser4 -P /dev/sdb  | gzip -9 > r4meta-sdb.gz
- metadata packed ok.

un-packed  # - I Unpacked r4 metadata with command as follows, metadata
unpacked ok.

# gunzip r4meta-sdb.gz
- metadata un packed ok.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Christian Kujau | 26 May 21:21 2016
Picon
Gravatar

Reiser4 wiki spam

FYI,

there appears to be an ongoing spam campaing against the Reiser4 
Wiki[0]. Bots seem to be able to overcome the reCaptcha when registering an 
account, but then luckily the ConfirmAccount extension steps in and I just 
marked a buch of account requests as spam.

If anyone was tryign to join the wiki and I mistook someone for a 
spam bot, please try again :-)

Thanks,
Christian.

[0] https://reiser4.wiki.kernel.org/
--

-- 
BOFH excuse #450:

Terrorists crashed an airplane into the server room, have to remove /bin/laden. (rm -rf /bin/laden)
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Georgios Tsalikis | 24 May 10:58 2016
Picon
Gravatar

Two Reiser4 FSs in the same HDD cause head seek panic?

I happened to format a rootfs partition and another one for /home with 
Reiser4. It proved to be a disaster. Apart from the slow boot times 
(expected from this drive) even after reaching a functional GUI the 
disk kept doing I/O  like crazy. When /home became Btrfs the issue 
ceased. My other computer that uses an entire drive formatted with 
Reiser4 is nice and silent as well.

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Georgios Tsalikis | 24 May 10:50 2016
Picon
Gravatar

How can checksums (node41) be of real help?

I suppose they are great for discovering corrupted files, but is there 
any way we can use them to retrieve a good copy of corrupted files?

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

doiggl | 23 May 14:11 2016
Picon

Could a Bugzilla reporting system be used {set up} to report reiser4 or reiser4progs bugs ?

Hello,

A Question:
Could a Bugzilla reporting system be used {set up} to report reiser4 or
reiser4progs bugs ?

I ask because its easier to keep track of bugs rather than
sending/finding/tracking them on a mailing list.

What are your thoughts on this ?
Thanks
--Glenn

ReiserFS example
################

https://bugzilla.kernel.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&component=Reiser4&component=ReiserFS&order=Importance&product=File%20System&query_format=advanced&short_desc=&short_desc_type=allwordssubstr

Content:

ID 	Product 	Comp 	Assignee 	Status 	Resolution 	Kernel Version 	Summary
	Changed
29162 	File Sys 	ReiserFS 	reiserfs-devel 	NEW 	---
	2.6.36,2.6.37,2.6.39,3.0 	Reiserfs hang with dataloss sometimes
	2016-02-16
34362 	File Sys 	ReiserFS 	reiserfs-devel 	NEW 	--- 	2.6.38.3
	Error-valued pointer dereferences 	2016-03-23
34372 	File Sys 	ReiserFS 	reiserfs-devel 	NEW 	--- 	2.6.38.3
	Error-valued pointer used in pointer arithmetic 	2016-03-23
104391 	File Sys 	ReiserFS 	reiserfs-devel 	NEW 	--- 	4.2.0
(Continue reading)

Mathieu Belanger | 15 May 03:17 2016

Reiser4 patch bumped to kernel 4.7-next20160513

Hi, I just ported Reiser4 to the current next version.

Change : 
- A small change occured in vmscan.c that broke the patch
- no more i_mutex in the inode struct. mutex_{lock,unlock}(&inode->i_mutex) replaced by inode_{lock,unlock}(inode).

I'm testing it tonight and will provide patchs by this night.

Note : I got the first power outrage since the barrier patch, about 2 minutes after compiling that new kernel
while writing this message and no problem / nothing lost.

--

-- 
Mathieu Belanger <admin <at> korinar.com>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Edward Shishkin | 6 May 13:04 2016
Picon

[PATCH] reiser4: fix up incorrect recalculation of maximal balance overhead


doiggl | 6 May 08:22 2016
Picon

r4 meta data query - commands to run on [r4metadata-sdb.gz] packed from [/dev/sdb]

Hello,
Edward ,Ivan

- on a copy of reiser4 unpacked metda-data [1]
Q1. Are there there tools or commands to do a detailed analyzses of a copy
of reiser4 unpacked metda-data and do a repairs on the copy of reiser4
metda-data [r4metadata-sdb] ?

Seems to have 'Wrong order of keys' problem

I can try new things out on a copy of reiser4 metadata and report results
back.
Thanks
--Glenn

[1]
I packed and un-packed and metadata using the following:

- packed reiser4 metadata via command:
# debugfs.reiser4 -P /dev/sdb  | gzip -9 > r4metadata-sdb.bz2

I unpacked metadata via command"
# gunzip r4metadata-sdb.bz2

# ll
-rw-r--r-- 1 root users 24733058856  Apr 14 04:24 [r4metadata-sdb]

Looks like binary data to me. [r4metadata-sdb]

-kernel 
(Continue reading)


Gmane