/ is no longer Reiser4 :(

2005-11-19 Thread John Gilmore
Following Han's comment about the deliterious effects of 6% fragmentation, I 
attempted a manual defrag of my hard disk.

While restoring the .tar file, I had nothing better to do than watch it. And a 
good thing too! It got a recurring oops. about every other minute or so, it 
would stop with a long kernel message than mostly scrolled off of the 
screen... I thought those where supposed to show up in a log files somewhere 
if possible, but I can't find it. And it should have been possible, as the 
computer continued to run just fine.

These oopses caused some sort of data corruption - root wouldn't boot properly 
afterwards. So I reformated as ext3 and untarred my root again. That worked 
fine, so I know it wasn't corruption of the tar file.

I took a photograph, and I'll try to type in some of it. Just looking at the 
names of the procudures, it looks like memory pressure made reiser4 flush, 
and then some of the lower level functions tried to allocate memory and 
failed. But since I don't have the top of the oops message, I can't tell.

Wait - I could've stopped the scrolling with ^S, scrolled back with ^pageup, 
and photoed the whole thing! Aaaargghh

Well, I'm not redoing it right now, I need to be getting to bed.

I may try it again later - but then maybe I'll update to 2.6.14-mm2 with patch 
from namesys first...

Here's the (tail end of the) oops message, sans addresses and offsets because 
I'm feeling lazy and I'm in a hurry:

mempool_alloc+0x3a/0xe0
__split_bio+0x128/0x190
in_drive_list
dm_request
generic_make_request
submit_bio
do_IRQ
reiser4_clear_page_dirty
write_jnodes_to_disk_extent
write_jnode_list
write_fq
flush_current_atom
flush_some_atom
writeout
reiser4_sync_inodes
writeback_inodes
background_writeout
pdflush
__pdflush
pdflush
background_writeout
kthread
kthread
kernel_thread_helper


Re: need opinions from sysadmins on where reiser4progs should install

2005-11-19 Thread rvalles
On Thu, Nov 17, 2005 at 05:06:43PM +0100, Philippe Gramoullé wrote:
 So should a crash occur and /usr becomes corrupted, well, at least / is 
 mounted and i could
 reiserfsck partitions right away, handy when the server is several thousand 
 kilometers away :)
 
 I expect to do the same for reiser4progs, so i wish that reiser4progs 
 utilities would install
 in /, and as such /sbin seems the best choice _to me_

When I run make install on something and haven't specified a prefix on
configure, I expect /usr/local to be used. If I wanted /, I'd have
specified that on configure time. If it installed in / by default, it
would, often, hit the sacred package-system managed area of the VFS
tree annoying people like me to a very great extend, so please don't.


pgptWAWCAb7TX.pgp
Description: PGP signature


Re: File as a directory - file-as-dir vs. link-dirs (again) - 3/3

2005-11-19 Thread Leo Comerford
On 11/19/05, Hubert Chan [EMAIL PROTECTED] wrote:
 P.S. your relational model can easily be expressed using file-as-dir
 (well, actually, just standard directories):

 /(something)/father-son/aardvark/father is a symlink to
   '/(whatever)/portrait/Mike')
 /(something)/father-son/aardvark/son is a symlink to
   '/(whatever)/portrait/Bob')


Yes absolutely. Yes, my relational model *does* uses standard
directories, with three differences.

1) foofs's internal implementation of link-directories and other
directories might be different. Or it might not. Entirely unimportant
at this level.

2) gc might treat some link-directories differently to
predicate-directories. (If Bob and Mike have been deleted, I don't
want /(something)/father-son/aardvark/ lying around.)

3)

 --
 Hubert Chan [EMAIL PROTECTED] - http://www.uhoreg.ca/
 PGP/GnuPG key: 1024D/124B61FA
 Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA
 Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.




--
Leo Richard Comerford - http://www.st-and.ac.uk/~lrc1 - accept no namesakes :)