similar to: Problems with Forms

We tried to migrate our app to rails 3/ruby 1.9.2 and now have huge problems with the initialization time of the rails instances. After a touch tmp/restart our passenger 2.2.4 needs several minutes(!!) to boot up 20 instances and to serve the first requests. We didn''t had that problem in rails 2. I would love to find out what is taking so long, but I don''t have any clue on

Hello (and Moin Moin) ;) I have currently a straith Problem ... I have our IMAP-Server migrated from an old cyrus the the current stable Version of dovecot. In the old configuration we organized many mails (e.g. root-Stuff) in Public Folders. They structure had nearly 5 folderlevels. After the complete migration an syncronize we switch complete to the dovecot setup. At this moment we have

Dear r-helpers, we have installation problems: Successful installation of R-0.63 base package on Solaris 2.5.1 with the SunSoft compilers f77, c version 4.2. We habe problems with the installation of further packages e.g. integrate from CRAN. R code works but the shared objects built from fortran code do not find the appropriate libs with functions like __pow_ii or __epx at runtime. We tried

Hi, in syslinux-386, I think I've found a problem in com32/lib/syslinux/load_linux.c that leads to cmdline being truncated unnecessarily when e.g. linux.c32 is used. The patch below fixes the problem for me. But I don't know, whether the patch is safe in all cases. I tried to reproduce the logic found in runkernel.inc, but I might have missed something. So, feel free to tell me

Dear helpers, I have strange results with levelplot: The following lines of code produce a figure with a strange gray horizontal line. Changing n to 9 the line vanishes almost - it stays in the colorbar. Any ideas? The pixel geometry of the lower half of the figure is wrong? ############################## n<-8 xyz<-expand.grid(x=seq(1,n),y=seq(1,n)) z<-matrix(0,n,n)

----- Original Message ----- From: "Bodo Thiesen" <bothie@gmx.de> To: <ext3-users@redhat.com> Sent: Monday, August 25, 2014 8:15 PM Subject: Re: filesystem > Hello Bill. [snip] > You're trying to understand what exactly? From the user point of view, > dir_index just makes directory accesses on very big directories faster. > When creating a new file, or

Hi, The method to boot an ISO using memdisk, memdiskfind and phram described in the wiki looks very promising to me. So, I looked into the sources trying to understand, how this works. Up to now, I could not find out how the memory containing the ISO image is preserved from being overwritten by the Linux kernel. Probably I'm missing something, could you please help me? Best regards, Bodo

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > The "lifetime writes" value has not been around forever, so if the > filesystem was originally created and populated on an older kernel > (e.g. using ext3) it would not contain a record of those writes. It was created as stable ext4 in the first place. So only if there was a stable ext4 release which didn't

Hello Bill again. Two things. First. I read this mailing list, so no need to send answers to me personally in copy. Second. I guessed it already, but now it got really obvious, that you didn't do your homework. Please search for your questions in your favorite search engine first. Yes, I know, that there is not much easy to understand information on ext2 (in all flavours) out there, but

> R code works but the shared objects built from fortran code do not find > the appropriate libs with functions like __pow_ii or __epx at runtime. I used to have endless trouble with __pow_ii which as I recall could be be fixed by the correct incantation of the mix of compiler libraries and LD_LIBRARY_PATH. It seemed to be extremely sensitive and never easy to get right. The problem is

* "Theodore Ts'o" <tytso@mit.edu> hat geschrieben: Hi Theodore. > That being said, it's pretty clear that portions of the inode table > and block group descriptor was badly corrupted. [...] Keith is not the first one with problems of this class and he will probably not be the last one. He later told us, that at first, mounting the file system still worked. And that

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > You can see in the ext4 superblock the amount of data that has been > written to a filesystem over its lifetime: > > Note that this number isn't wholly accurate, but rather a guideline. Is is more like a completely bogus value at best: # LANG=C df -h / | grep root /dev/root 3.7T 3.6T 73G 99% / # grep [0-9]

I hope this is the right list. I have created an ext2 filesystem and removed the dir_index feature. I don't know if this kind of experimentation is going to help me learn something about filesystems or not. Well what is dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I remove? Htree. I guess it can always be put back and it's on an experimental filesystem.

Hi Bodo and Ted, Thank you both for your responses; they confirm what I thought might be the case. Knowing that I can try to proceed with your suggestions. I do have some followup questions for you: On Sun, Jun 01, 2014 at 09:05:09PM -0400, Theodore Ts'o wrote: > Unfortunately, there has been a huge number of bug fixes for ext4's > online resize since 2.6.32 and 1.42.11.

Hello there, I have some problem with my filesystem. #df -h ... /dev/da0s1e 288M 265M -208.0K 100% /var ... #du -h /var .. 19M /var .. Does anybody has an idea what Im supposed to do? Thank you. --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo.

On Thu, Oct 16, 2014 at 11:01:35PM +0200, Bodo Thiesen wrote: > > Since it never get's updated unless the file system is unmounted, it can > only be used for a 24 hours test by mounting the file system now, > unmounting it 24 hours from now and then taking the difference. It also gets updated if the file system syncfs(2) or sync(2) system call. But if you crash, any writes since

Hi, working with R, version 0.63.0, I was successful to dyn.load fortran90 subroutines on a Solaris 2.6, as long as they are more or less in conformity with f77. It was not possible to work with statements like REAL,DIMENSION(:) :: d or x=SUM(y). REAL,DIMENSION(1:10) :: d is possible. We compiled R with f77. Is it possible with real f90 routines or is is in any conflict with the shared

* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > I hope this is the right list. I have created an ext2 filesystem and > removed the dir_index feature. I don't know if this kind of experimentation > is going to help me learn something about filesystems or not. Well what is > dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I >

Hello, I found serveral discussions about the Zyxel ePhone Prestige P2000W and the WiSip from Pulver Innovations on this mailings list but still have some questions: 1) are there other affordable wireless SIP Phones on the market? I haven't seen or found anything else till now ... 2) is p2000w and wisip the same hardware?? so could I use firmware from both companies regardless of what

Hello ext users, in a recurrent need to be able to traverse large filesystems (10-350M inodes) backed by spindle-based RAID arrays, I tried several solutions (like intercepting readdir and sorting by inode, playing with cache hints, and such), to no avail. Since I'm mostly facing ext3 and ext4 filesystems, I wrote a tool based on libe2fs which replaces the 'find /' part by