similar to: Change defaults to data=journal on /

Can anyone tell me if there has been testing of using an SMP kernel on a UP machine and if that is bad? I have an ext3 filesystem that keeps getting corrupt. Certain directories only get I/O errors, trying to access beyond the end of the device. Thanks, Gabe

On 08/05/2018 4:50 PM, Steven Nydick wrote: > It also does the same thing if the factor is not on the first level of > the list, which seems to be due to the fact that the islistfactor is > recursive, but if a list is a list-factor, the first level lists are > coerced into character strings. > > > x <- list(list(factor(LETTERS[1]))) > > unlist(x) > Error in

On 08/05/2018 2:58 PM, Duncan Murdoch wrote: > On 08/05/2018 1:48 PM, Steven Nydick wrote: >> Reproducible example: >> >> x <- list(list(list(), list())) >> unlist(x) >> >> *> Error in as.character.factor(x) : malformed factor* > > The error comes from the line > > structure(res, levels = lv, names = nm, class = "factor") >

Reproducible example: x <- list(list(list(), list())) unlist(x) *> Error in as.character.factor(x) : malformed factor* What should happen: unlist(x) > NULL R.version platform x86_64-apple-darwin15.6.0 arch x86_64 os darwin15.6.0 system x86_64, darwin15.6.0 status major 3 minor 5.0 year 2018 month 04 day

I do not have access to the bug reporting system. If somebody can get me access, I can create a formal bug report. The latter issues seem like duplicates of: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=12572 (with slightly different output), but as that bug was reported nearly 10 years ago, it might be worth creating an update under R version 3. I could not find the first issue when

It also does the same thing if the factor is not on the first level of the list, which seems to be due to the fact that the islistfactor is recursive, but if a list is a list-factor, the first level lists are coerced into character strings. > x <- list(list(factor(LETTERS[1]))) > unlist(x) Error in as.character.factor(x) : malformed factor However, if one of the factors is at the top

Hi, I'm formatting a flash with ext3, but I need to move the journaling file (/.journal) in the flash to prevent it's corruption. In previous message I read that it's possible (https://www.redhat.com/archives/ext3-users/2004-March/msg00009.html), but I can't find any /.journal in my ext3 fs. How can move the journaling file in the flash without /.journal file?? Thanks

Forgive my novice question, but I am a new student of Linux working on presenting the ext3 journaling filesystem to my class. I seek any advice on how to visibly demonstrate (including a purposeful crash of a Linux box) the benefits of ext3 over ext2. I am not worthy to lick the bootstraps of this group, but I beg for any help! The problem I am having extends to even locating the .journal file

Hi, I'm running 2.4.9-ac7 with ext3 compiled in, and I ran across this problem. Now that I look back, it makes sence, but it wasn't obvious at first... I wanted to change the journal mode on my / partition, so I changed my fstab to: /dev/hda1 / ext3 defaults,errors=remount-ro,data=journal 0 1 as well as several other partitions, and rebooted. After rebooting I had a read only / that I

Hi, We are currently doing SpecSFS comparison benchmarking to evaluate advantages of FS journaling to NVRAM card versus journaling to hard disks. We compare NFS performance for Linux file server with ext3 file system in ?data=journal? mode for three different locations of the file system journal: - inside main file system - on a dedicated HD - on an NVRAM PCI card The file system is

Hello what is the limitation of inode and journaling on 32 bit ext3 file system. what about 64 bit. Thanks

EXT3 developers: I am curious, if EXT3 is currently being used on the root partition in "data=ordered" mode (the default as I understand), and I want to have the it come up in data=journal mode, how do you effectuate this conversion? I would also be curious how to know if anything special is required for doing so for the /boot partition as well. I believe that with the /home partition,

Hello I try again. Can anybody of you acknowledge or not if mode data=journal in ext3 is safe to use in Linux kernel 2.6.x? Wee need to have a very consistent and integrity for our filesystem, and it would then be desired to journal both data and metadata. But if this mode can corrupt the filesystem as both Phil White and Nicolas Kowalski has experienced, it may be more advised to use mode

Hi! Is there a way to view ext3 filesystem's maintained journal (in a human-readable-format)? I ask, because i have had a server crash before and now i'm wondering if i might take a look at last things that my server did straight before crash. I guess clarifying log insertions might be lost before buffers were flushed to disk. Thx.

Hi, I'd like to use a flash drive as a journal device, with the purpose of keeping the main disk drive spun down as long as possible. I have a couple of questions: 1) Does the journaling code spread write accesses to the journal device evenly, as I hope, or are there blocks that are particularly "hot"? I.e., do I have to worry about the flash device dying quickly because of

Hello, Is there some document about ext3 performance tuning and choosing the right type and size of journal? Except RedHat's white paper. From what I read I understood that for typical operations data=ordered is prefered. For the cases when there are many writes not appending to files data=journal is the choice. And if I want to get the most performance or in case where program is doing

Hi, Im wondering what would be a good size on the journal file for a data=journal ext3 ? I can't find any reference to a "standard" value for other then ordered (8192 blocks). Please include my email in replies, Thanks in advance. -- echo '[q]sa[ln0=aln256%Pln256/snlbx]sb382793634903snlbx806007844 59087snlbx71765988876376snlbx11172185121099snlbx'|\dc

Hi. I'm using e2fsprogs 1.23 on a Roswell system with a patched 2.4.7 kernel (using patch ext3-2.4-0.9.5-247) and am trying to create an ext3 filesystem whose journal is located on another device. The incantation I'm trying is: mke2fs -j -J device=/dev/hdc2 /dev/hdc3 I keep getting an error along the lines of "mke2fs: Journal superblock not found". I've tried creating

A scsi error (caused possibly by a loose cable) has left the processes accessing my ext3 file system hung in an unkillable state after it triggered an assert in ext3's journaling layer. I assume my only recourse at this point is to reboot. Please correct me if I'm wrong. Log messages appended. Thanks, -Jim Nov 21 04:04:04 attila kernel: SCSI disk error : host 0 channel 0 id 5 lun 0

Hi all, Man page of tune2fs says that max journal size is 102,400 filesystem blocks, which translates to ~100MB with 1kb blocks or ~400MB with 4kb block. I wonder - why this limitation exists? Now that relatively cheap ssd devices exist (gigabyte iRam) that offer up to 4GB of space, it would be extremely useful to use whole capacity of such device for full data journaling. -- Jure Pe?ar