My pic links

2005-04-12 Thread Anibal Arnold
Screenname: Erica1976 
Age: 28 
Status: Single 
Gender: F 

Contact details and pics can be found here:

http://www.joryxondan.com/pics/





Re: Bug report

2005-04-12 Thread studdugie
Unfortunately I can't easily and faithfully reproduce the problem
because the data set I was working against got destroyed in the
process and it's going to take a while to generate a data set of the
same size. I've tried some simple hacks to reproduce parts of the
original run but they were unable to elicit failure, so I'm convinced
that I need a data set of a similar size as the original.

On a different note, why does reiser4 take so long to mount compared
to other filesystems? I'm talking about 15 or more seconds to mount a
745GB partition.

On Apr 11, 2005 11:30 AM, Vladimir Saveliev <[EMAIL PROTECTED]> wrote:
> Hello
> 
> On Mon, 2005-04-11 at 18:07, studdugie wrote:
> > Hello. I've just joined the reiserfs mailing list today because I need
> > to report a bug in reiser4. If this list is not the appropriate place
> > to report bugs, firstly, my apologies. Finally, I would appreciate
> > some guidance about the appropriate outlet.
> >
> > I'm in quasi testing of reiser4 mode insofar as this box is concerned
> > and the specific app that trigged the failure but eventually I'm going
> > to need the app to complete w/o failure. If you (the reiser gurus)
> > think this is the sort of thing that has already been solved or can be
> > wrapped up in a short amount of time I would be glad to continue
> > pounding reiser4 and giving feedback.
> >
> 
> Can you describe how to reproduce this problem?
> This looks like a problem we encounter from time to time.
> 
> > 
> > [ cut here ]
> > kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:32!
> > invalid operand:  [#1]
> > SMP
> > Modules linked in:
> > CPU:0
> > EIP:0060:[]Not tainted VLI
> > EFLAGS: 00010282   (2.6.11-mm2)
> > EIP is at get_exclusive_access+0x2f/0x40
> > eax: f2d5035c   ebx: f2d503c4   ecx: f73c3c98   edx: e5946e80
> > esi: f2d5035c   edi: f7df1d68   ebp: f7df1f3c   esp: f7df1d34
> > ds: 007b   es: 007b   ss: 0068
> > Process pdflush (pid: 111, threadinfo=f7df task=c43a3020)
> > Stack: c0210be1 f2d5035c f7df1f3c c0208148 c04c8ba0 f2d503c4 c01ea5b1 
> > f2d503c4
> >f7344c00 f7df1e6c   0008   
> > 
> >       
> > 
> > Call Trace:
> >  [] pre_delete_unix_file+0x21/0x50
> >  [] kill_cursors+0x18/0x20
> >  [] delete_inode_common+0x191/0x200
> >  [] drop_common+0x49/0x50
> >  [] reiser4_drop_inode+0x20/0x40
> >  [] iput+0x63/0x90
> >  [] generic_sync_sb_inodes+0x217/0x2d0
> >  [] pdflush+0x0/0x30
> >  [] reiser4_sync_inodes+0x4c/0xa0
> >  [] sync_sb_inodes+0x2e/0x40
> >  [] writeback_inodes+0xec/0x100
> >  [] wb_kupdate+0x96/0x110
> >  [] __pdflush+0xbb/0x190
> >  [] pdflush+0x26/0x30
> >  [] wb_kupdate+0x0/0x110
> >  [] pdflush+0x0/0x30
> >  [] kthread+0xba/0xc0
> >  [] kthread+0x0/0xc0
> >  [] kernel_thread_helper+0x5/0x10
> > Code: ff 8b 44 24 04 21 e2 8b 12 8b 92 b8 04 00 00 8b 52 44 8b 52 0c
> > 85 d2 75 12 ba 01 00 ff ff f0 0f c1 10 85 d2 0f 85 0c 11 00 00 c3 <0f>
> > 0b 20 00 c0 81 47 c0 eb e4 8d b4 26 00 00 00 00 8b 44 24 04
> > 
> >
> > Here is some miscellaneous output from the dmesg command that
> > may/maynot have a bearing on the issue.
> > 
> > reiser4[java(7213)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 16384
> > reiser4[java(7213)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 32768
> > reiser4[java(7213)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 65536
> > reiser4[java(7599)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 16384
> > reiser4[java(7599)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 32768
> > reiser4[java(7599)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 65536
> > reiser4[ent:dm-0!(4791)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 16384
> > reiser4[ent:dm-0!(4791)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 32768
> > reiser4[ent:dm-0!(4791)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 65536
> > reiser4[ktxnmgrd:dm-0:r(4790)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 16384
> > reiser4[ent:dm-0!(4791)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 16384
> > reiser4[ent:dm-0!(4791)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 32768
> > reiser4[java(7858)]: commit_current_atom
> > (fs/reiser4/txnmgr.c:1147)[nikita-3176]:
> > WARNING: Flushing like mad: 16384
> > reiser4[java(7858)]: commit_current_atom
> > (fs/reiser4/tx

Re: Yet another reiserfs

2005-04-12 Thread E.Gryaznova
Hello.
Joachim Zobel wrote:
Am Montag, den 11.04.2005, 22:04 +0400 schrieb E.Gryaznova:
 

Would you please send the following commands outputs?:
# dmsetup deps
# dmsetup status
# dmsetup info
# pvdisplay --map
# lvdisplay --map -vv
# ls -l /dev/vg (and /dev/mapper)
   

See the attached file reiserfs.log
The devices 
volg2-logv4: 1 dependencies : (22, 3)
volg2-logv3: 1 dependencies : (22, 3)
volg2-logv2: 1 dependencies : (22, 3)
where created after the incident. 
One of them had a successful (some files lost) reiserfsck --rebuild-tree
after dd-ing the bad /dev/volg-raid1/logv1 on it. 

lvdisplay --map -v did some stderr output, which is attached as
lvdisplay.err
#cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 hda2[0] hdc2[1]
 3903680 blocks [2/2] [UU]
Sincerely,
Joachim
 

I have checked lvm, it looks ok. Probably this is hardware problem.
If you need our  assistance in further investigation, please visit our 
support page http://www.namesys.com/support.html .

Thanks,
Lena




Re: Yet another reiserfs

2005-04-12 Thread David Masover
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

E.Gryaznova wrote:
> Hello.
> 
> Joachim Zobel wrote:
> 
>> Am Montag, den 11.04.2005, 22:04 +0400 schrieb E.Gryaznova:
>>
>>  
>>
>>> Would you please send the following commands outputs?:
>>> # dmsetup deps
>>> # dmsetup status
>>> # dmsetup info
>>> # pvdisplay --map
>>> # lvdisplay --map -vv
>>>
>>>
>>> # ls -l /dev/vg (and /dev/mapper)
>>>
>>>   
>>
>>
>> See the attached file reiserfs.log
>>
>> The devices volg2-logv4: 1 dependencies : (22, 3)
>> volg2-logv3: 1 dependencies : (22, 3)
>> volg2-logv2: 1 dependencies : (22, 3)
>> where created after the incident. One of them had a successful (some
>> files lost) reiserfsck --rebuild-tree
>> after dd-ing the bad /dev/volg-raid1/logv1 on it.
>> lvdisplay --map -v did some stderr output, which is attached as
>> lvdisplay.err
>>
>> #cat /proc/mdstat
>> Personalities : [raid1]
>> md0 : active raid1 hda2[0] hdc2[1]
>>  3903680 blocks [2/2] [UU]
>>
>> Sincerely,
>> Joachim
>>  
>>
> 
> I have checked lvm, it looks ok. Probably this is hardware problem.
> If you need our  assistance in further investigation, please visit our
> support page http://www.namesys.com/support.html .

This just suddenly became an issue for me -- I'm about to do dm-raid.
What's a good filesystem stress-testing tool?  (I want to do Reiser4.)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQlx6V3gHNmZLgCUhAQJxjw/+PDsstdWS2VDX+bLSaBwBDxZvIMaYN8V0
IdgmjSsOcqSLNb70J3es6HJMTrAxWFJ7YjQtQ+J7xqvtYJlMDr/EafFB7nLxk9eP
6SnrXk5LAp00YLBS66s6Rxz+5YZaRNVHl5MRNu5Hz3dYe5+Jk08FgnlDMMA0wKD2
6y/qvNAYP3DdxNlSKx/bo6b+nTQZaLTh8FV2Ew5g5xdXtyb0R1xrBx06njJZwnlb
w8MMnR/Uz1b8rJwCP4fEzoZulrtgbNE+oe9GRF+uujiTD4Jb7RAXyokBTGutiO1d
ROmC8OvmjmNo9LU0c+9waUP0NMd+nOwqpM7vToTX3Vbi3B1F9v+7B4FAQRDIlvle
opVV7GhzsoRoRMHc/Dc/PENVk6FylHaWqFWCGfqRtDFnUeGyON5E221B8ppQOsFa
lKjSSszJhhG/2ZuZIfkXf2k2Z9vyi+Z0AhHjEJ1/lI8dGKGSEJskoukhQg04SGsl
0NjQAP8ezF/MnFcZiNLBilxquw5vq8xpJ5t+YlcjPnnA7YjWeYmssOajuUV2HPHg
+D/y7yv0P5ZjBMuIYRKT8XPu3otmR8krTH4cFI0KzCGH13hJm8h+O25N+9Bn1MUU
6NYGM4v8DFrM+3YGNdhAMakf9ZxjmiRnHaj9aukfFZo2hZfCQiN+0Y02p0SEge52
l0Poq8b7Sho=
=O+hc
-END PGP SIGNATURE-