Hi
I am trying out Reiser4 snapshot from August 26th.
I've putted my kde cvs sources on the new partition and compile from reiser4
now.
After some time processes hang when accessing this disk. I cannot do
anything on it but I also don't get any errormessage.
Umount, bash autocomletion and things like that don't work. Normal df and
mount are working btw.
Here are the line from strace when I call ls:
open("/lib/libattr.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\r\0\000"..., 512)
= 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=10668, ...}) = 0
old_mmap(NULL, 13736, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x401af000
old_mmap(0x401b2000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x2000) = 0x401b2000
close(3) = 0
munmap(0x40014000, 94548) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) =
0
setrlimit(RLIMIT_STACK, {rlim_cur=2044*1024, rlim_max=RLIM_INFINITY}) = 0
getpid() = 9293
rt_sigaction(SIGRTMIN, {0x401676a0, [], SA_RESTORER, 0x4006cc38}, NULL, 8) =
0
rt_sigaction(SIGRT_1, {0x401676d8, [], SA_RESTORER, 0x4006cc38}, NULL, 8) =
0
rt_sigaction(SIGRT_2, {0x4016778c, [], SA_RESTORER, 0x4006cc38}, NULL, 8) =
0
rt_sigprocmask(SIG_BLOCK, [RTMIN], NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [33], NULL, 8) = 0
_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff44c, 32, (nil), 0}) = 0
brk(0) = 0x805a000
brk(0x807b000) = 0x807b000
brk(0) = 0x807b000
ioctl(1, SNDCTL_TMR_TIMEBASE, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TIOCGWINSZ, {ws_row=50, ws_col=124, ws_xpixel=0, ws_ypixel=0}) = 0
open("/dev/null", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = -1 ENOTDIR (Not a
directory)
open(".", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=35, ...}) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
getdents64(3,
< hang >
Should I enable debugging to get some info ? What should I enable there ?
CONFIG_REISER4_FS=y
# CONFIG_REISER4_FS_SYSCALL is not set
CONFIG_REISER4_LARGE_KEY=y
# CONFIG_REISER4_CHECK is not set
CONFIG_REISER4_USE_EFLUSH=y
# CONFIG_REISER4_BADBLOCKS is not set
thanks
Felix
--
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualit?tssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
Felix Seeger writes:
> Hi
>
> I am trying out Reiser4 snapshot from August 26th.
> I've putted my kde cvs sources on the new partition and compile from reiser4
> now.
>
> After some time processes hang when accessing this disk. I cannot do
> anything on it but I also don't get any errormessage.
If there anything in /var/log/messages, or wherever your kernel log is
stored?
>
> Umount, bash autocomletion and things like that don't work. Normal df and
> mount are working btw.
Nikita.
On Friday 29 August 2003 14:28, you wrote:
> Felix Seeger writes:
> > Hi
> >
> > I am trying out Reiser4 snapshot from August 26th.
> > I've putted my kde cvs sources on the new partition and compile from
> > reiser4 now.
> >
> > After some time processes hang when accessing this disk. I cannot do
> > anything on it but I also don't get any errormessage.
>
> If there anything in /var/log/messages, or wherever your kernel log is
> stored?
No, nothing. At least in messages, kern.log and syslog.
But I found the problem. My old dir (on a reiser3 partition) was:
~/download/kde3/cvs which got renamed to old_cvs
My new reiser4 dir is
~/download/kde3/new_cvs
Since there are some full paths (maybe from make) I created a symlink
~/download/kde3/cvs
I removed that link and readded the one to the old partition, all make
processes stopped and I can access the partition again.
Note that I cannot reproduce this if I create just the symlink. That works
fine here, maybe I have to run make again to get the problem back.
> > Umount, bash autocomletion and things like that don't work. Normal df
> > and mount are working btw.
>
> Nikita.
have fun
Felix
--
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualit?tssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
On Friday 29 August 2003 15:14, Felix Seeger wrote:
> On Friday 29 August 2003 14:28, you wrote:
> > Felix Seeger writes:
> > > Hi
> > >
> > > I am trying out Reiser4 snapshot from August 26th.
> > > I've putted my kde cvs sources on the new partition and compile from
> > > reiser4 now.
> > >
> > > After some time processes hang when accessing this disk. I cannot do
> > > anything on it but I also don't get any errormessage.
> >
> > If there anything in /var/log/messages, or wherever your kernel log is
> > stored?
>
> No, nothing. At least in messages, kern.log and syslog.
>
> But I found the problem. My old dir (on a reiser3 partition) was:
> ~/download/kde3/cvs which got renamed to old_cvs
> My new reiser4 dir is
> ~/download/kde3/new_cvs
>
> Since there are some full paths (maybe from make) I created a symlink
> ~/download/kde3/cvs
>
> I removed that link and readded the one to the old partition, all make
> processes stopped and I can access the partition again.
> Note that I cannot reproduce this if I create just the symlink. That works
> fine here, maybe I have to run make again to get the problem back.
The mount hangs again. This time without a symbolic link.
umount -f /dev/hdb6 gives:
umount2: Device or resource busy
umount: /dev/hdb6: not mounted
umount: /home/hal/download/kde3/cvs: Illegal seek
Prozesses that use that partition:
# lsof | grep kde3/cvs
cc1plus 31258 hal cwd DIR 3,70 33 133147
/home/hal/download/kde3/cvs/kdelibs/kstyles/keramik
cc1plus 31258 hal mem REG 3,70 85595 248079
/home/hal/download/kde3/cvs/kdelibs/kstyles/keramik/keramik.cpp
cc1plus 31258 hal mem REG 3,70 23725 135815
/home/hal/download/kde3/cvs/kdelibs/config.h
rm 31413 hal cwd DIR 3,70 33 133147
/home/hal/download/kde3/cvs/kdelibs/kstyles/keramik
I can't kill them, nothing in the logs again.
> > > Umount, bash autocomletion and things like that don't work. Normal df
> > > and mount are working btw.
> >
> > Nikita.
>
> have fun
> Felix
--
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualit?tssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post
On Friday 29 August 2003 14:28, Nikita Danilov wrote:
> Felix Seeger writes:
> > Hi
> >
> > I am trying out Reiser4 snapshot from August 26th.
> > I've putted my kde cvs sources on the new partition and compile from
> > reiser4 now.
> >
> > After some time processes hang when accessing this disk. I cannot do
> > anything on it but I also don't get any errormessage.
>
> If there anything in /var/log/messages, or wherever your kernel log is
> stored?
Ok, after playing around with umount and kill I finally got some error
messages. Don't know if they are important:
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 16384
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 32768
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 65536
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 131072
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 262144
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 524288
reiser4[ktxnmgrd:run(28206)]: commit_current_atom (fs/reiser4/txnmgr.c:1010)
[nikita-3176]:
WARNING: Flushing like mad: 1048576
...
> > Umount, bash autocomletion and things like that don't work. Normal df
> > and mount are working btw.
>
> Nikita.
Felix