search for: tind

Dear R-helpers, I am using the package "gee" to run a marginal model. Here is the output. In my simulated data, both x and z are time-varying, so I include their interaction terms with time indicator (i.e. tind=0, if time 1, and 1 if time 2) The data is simulated, so the true parameter of z both at time 1 and time 2 is 5, which is very close from the model output for time 1, z = 5.0757760, and for time 2, z is 5.0757760-0.6379866 = ~5 > model=gee(y~x+z+x*tind+z*tind, family=gaussian(link = "ident...

...# reads entire matrix latmat = get.var.ncdf(nc=tg.ncdf,varid="latitude") # ditto timearr = get.var.ncdf(nc=tg.ncdf,varid="time") # reads entire time array targettime = julian(x=1, d=1, y=2002, origin=c(month = 1, day = 1, year = 1950)) inds = (1:dim(timearr)) tind = inds[targettime == timearr] ndims = tg.ncdf$var[['data']]$ndims varsize = tg.ncdf$var[['data']]$varsize start = c( 1, 1, tind) count = c(varsize[1], varsize[2], 1) # Read in data slice: tg.data = get.var.ncdf(nc=tg.ncdf,varid="data",st...

Hello everybody, It's my first post on this mailing list, and my english is not very good. I hope this is not a problem for you. I have successfully install a lot of tind under windows XP, but a friend made one installation (I help with mail) and he have this error when he try to run tincd : --- system call 'listen' failed: l'operation tent? n'est pas prise en charge pour le type d'objet r?f?renc? --- Apparently the installation is ok. He h...

How big is a file that e2fsck considers it to be a large file? 814611 blocks used (42.79%) 0 bad blocks 1 large file <----- that Thanks John Nelson

Let me preface this by saying "Yes, I know *nix filesystems don't need to worry about fragmentation". That said, is there a way to check the overall level of fragmentation of a live ext3 filesystem? I know about filefrag, but that's for specific files. And I think e2fsck tells you, but only if you take the filesystem offline for the scan. Is there anything that will give

...ck and trible indirect block needs to be updated, and copy them each in one of the "deletion blocks", but only if they are not already in one of the "deletion blocks". Update the copies in the "deletion blocks" leaving the original ind, dind and tind blocks alone. All this is done in one transaction. 3.3. Repeat 3.2. as long as there are still blocks beyond the 12 blocks boundary. 3.4. Free the last blocks of the inode, and set dtime to zero (to prevent later recoveries from staring over again). Again, one transaction. 3.5....

...ctivity Pass 3A: Optimizing directories Optimizing directories: 16430 Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda8: ***** FILE SYSTEM WAS MODIFIED ***** 615 inodes used (1%) 17 non-contiguous inodes (2.8%) # of inodes with ind/dind/tind blocks: 251/10/0 31720 blocks used (16%) 0 bad blocks 0 large files 519 regular files 87 directories 0 character device files 0 block device files 0 fifos 6 links 0 symbolic links (0 fast symbolic links) 0 sockets ---...

While I untar a large archive on xfs , ext3 (ver 1.3 and ver 1.4) file systems , on ppc processor and kernel ver 2.6.21 , I get an error. Also sometimes, on ext3 (1.3 and 1.4) the file system goes read-only while untarring. The same tar file when untarred on a i386 machine works properly. ERROR: -------------- tar: Skipping to next header gzip: stdin: invalid compressed data--crc error tar:

...Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 10880 inodes used (100%) 1025 non-contiguous inodes (9.4%) # of inodes with ind/dind/tind blocks: 702/80/0 1229437 blocks used (44%) 0 bad blocks 0 large files 9925 regular files 815 directories 0 character device files 0 block device files 0 fifos 3 links 131 symbolic links (131 fast symbolic links) 0 sockets -------- 1...

Having just spent a day trying to recover a deleted ext3 file for a friend, I'm wondering about this way of maintining undelete information in ext3, like is done for ext2: The last step in the deletion process would be to put back the (previously zeroed) block pointers. Since it gets logged to the journal, I _think_ that this should be safe. The worst that would happen is that, if the plug

...Directories count wrong for group #12 (12, counted=10). Fix? no Directories count wrong for group #15 (11, counted=10). Fix? no /tmp: ********** WARNING: Filesystem still has errors ********** 1506 inodes used (0%) 234 non-contiguous inodes (15.5%) # of inodes with ind/dind/tind blocks: 139/17/0 119586 blocks used (22%) 0 bad blocks 0 large files 1119 regular files 316 directories 0 character device files 0 block device files 0 fifos 0 links 4 symbolic links (4 fast symbolic links) 39 sockets -------- 1...

...rectories count wrong for group #228 (0, counted=139). Fix? no Free inodes count wrong (3759253, counted=3348765). Fix? no hdb1.img: ********** WARNING: Filesystem still has errors ********** 11 inodes used (0%) 7136 non-contiguous inodes (64872.7%) # of inodes with ind/dind/tind blocks: 50303/388/0 126175 blocks used (1%) 0 bad blocks 0 large files 377976 regular files 30868 directories 0 character device files 0 block device files 13 fifos 48 links 1632 symbolic links (1631 fast symbolic links) 0 sockets --------...

...Directories count wrong for group #12 (12, counted=10). Fix? no Directories count wrong for group #15 (11, counted=10). Fix? no /tmp: ********** WARNING: Filesystem still has errors ********** 1506 inodes used (0%) 234 non-contiguous inodes (15.5%) # of inodes with ind/dind/tind blocks: 139/17/0 119586 blocks used (22%) 0 bad blocks 0 large files 1119 regular files 316 directories 0 character device files 0 block device files 0 fifos 0 links 4 symbolic links (4 fast symbolic links) 39 sockets -------- 1...

well, the next place to go, if fsck isn't enough would be to to try debugfs(1) man debugfs. On Wed, Nov 18, 2015 at 8:39 PM, Boylan, Ross <Ross.Boylan@ucsf.edu> wrote: > I guess some of the trouble was that the virtual disk was mounted > read-only at the VM level. When I mounted read/write I was able to do > fsck, which gave messages about replaying the logs and a couple

...s... [root@pro180 root]# fsck.ext2 -vf /dev/hdf2 e2fsck 1.27 (8-Mar-2002) Pass 1: Checking inodes, blocks, and sizes Error while scanning inodes (0): The inode is from a bad block in the inode table 105597 inodes used (2%) 0 non-contiguous inodes (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 2538385 blocks used (26%) 0 bad blocks 0 large files 0 regular files 0 directories 0 character device files 0 block device files 0 fifos 1 link 0 symbolic links (0 fast symbolic links) 0 sockets -------- 1...

...04) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 11 inodes used (0%) 1 non-contiguous inode (9.1%) # of inodes with ind/dind/tind blocks: 0/0/0 1967476 blocks used (1%) 0 bad blocks 1 large file 0 regular files 2 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets -------- [root at...

...g directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information sg500misc: ***** FILE SYSTEM WAS MODIFIED ***** 33658 inodes used (0.23%) 3325 non-contiguous files (9.9%) 24 non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 25055/2723/2 21136610 blocks used (71.72%) 0 bad blocks 6 large files 31899 regular files 1698 directories 0 character device files 0 block device files 0 fifos 0 links 52 symbolic links (52 fast symbolic links) 0 sock...

Hi there, For years I've been using the ext3 file system without to think that it can ever gets broken so bad. This was until last week when a box that I have running Linux from a SanDisk CF went down. Since then I am struggling with this CF trying to understand what is happening. The CF is SanDisk ultra II 1GB. On this I have 4 partitions all of them with ext3: boot / swap

Additionally to the problems I reported earlier, I'Ve discovered another problem with my server/client setup. find reports find: WARNING: Hard link count is wrong for ./foo: this may be a bug in your filesystem driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched. in one directory and if I

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *