similar to: SV: mode data=journal in ext3. Is it safe to use?

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

Hello I can see several postings on this mailing-list that people have problem with mounting ext3 partition with mode data=journal. See URL's: https://www.redhat.com/archives/ext3-users/2004-March/msg00000.html https://www.redhat.com/archives/ext3-users/2004-March/msg00050.html We are going to use ext3 on a Compact Flash disk in true IDE mode. We need this filesystem to be as safe and

Hello! I'm using a CompactFlash as storage device. Since those CF cards only have limited write cycles (CF does wear-levelling by itself, but you don't want to write too many timet so the card) i was wondering by what a factor the journaling of ext3 increases the write accesses to the CompactFlash compared to ext2. Thanks a lot already for your help! Sincerely Chris Braun

I have now added a user and the hash apirs in the passwd... :] but when I try to log in but it just don't work :/ Can someone give a suggestion? This is my smb.conf... I guess theres a chance that its where the problem comes in 2 play :) [global] workgroup = Nost encrypt passwords = yes smb passwd file = /usr/local/private/smbpasswd unix password sync = yes

I hope this EIP can enlightend the developers: Jun 10 10:28:59 shawarma kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000019 Jun 10 10:28:59 shawarma kernel: printing eip: Jun 10 10:28:59 shawarma kernel: c0181d47 Jun 10 10:28:59 shawarma kernel: *pde = 00000000 Jun 10 10:28:59 shawarma kernel: Oops: 0000 [#1] Jun 10 10:28:59 shawarma kernel: Modules linked in:

> Changed ownerships seem to happen in larger groups or > batches. The most frequent occurence is that "user A" finds > that his homedir and *all* files and dirs under it are > suddenly owned by "user B". Also files under "user A"'s > homedir which where previously owned by root (some > auto-generated statistics are owned by root) get their >

On 11/03/16 12:08, Andy Walsh wrote: > Hi, > > i try to create a openWRT Samba 4.3 package and stumbled across the fact > that samba 4.3 will create those message socks inside the private-dir. That > results in creating entries inside /etc/samba/msg.sock. > > On openWRT /var is a tempFS in ram, so anything there is not a problem > regarding nvram and wear leveling. Yet the

On Mon, Feb 8, 2016 at 3:18 PM, <m.roth at 5-cent.us> wrote: > Chris Murphy wrote: >> DBAN is obsolete. NIST 800-88 for some time now says to use secure erase >> or enhanced security erase or crypto erase if supported. >> >> Other options do not erase data in remapped sectors. > > dban doesn't? What F/OSS does "secure erase"? And does it do

Rowland penny <rpenny <at> samba.org> writes: > > On 11/03/16 12:08, Andy Walsh wrote: > > Hi, > > > > i try to create a openWRT Samba 4.3 package and stumbled across the fact > > that samba 4.3 will create those message socks inside the private-dir. That > > results in creating entries inside /etc/samba/msg.sock. > > > > On openWRT

Hi, i try to create a openWRT Samba 4.3 package and stumbled across the fact that samba 4.3 will create those message socks inside the private-dir. That results in creating entries inside /etc/samba/msg.sock. On openWRT /var is a tempFS in ram, so anything there is not a problem regarding nvram and wear leveling. Yet the root uses a jffs2 overlay. So while those message socks have no size, jffs2

Hi, maybe someone could help me out here: I have a broken disk with serveral partitions (1-3 primary, 4 extended and 5-6 logical). I am able to get access to the primary partions and already recovered the data. I can see all partitions using fdisk -l /dev/hdc. But I cannot mount the logical ones: mount -t ext3 /dev/hdc5 /mnt mount: wrong fs type, bad option, bad superblock on

Hello i had the same problem 2 days ago :) and the nice people here tolt me what to do .. >smbpasswd -a username(valid unix) and then define the password this shuld do the job :) Ps -axe |grep Ketil 79 ? S 1:09 /usr/sbin/klogd -c 3 -x PWD=/ CONSOLE=/dev/console -x (Ketil Braun Larsen) -----Oprindelig meddelelse----- Fra: Leva [mailto:leva@interware.hu] Sendt: 16. marts

Hi, I don''t know if it''s already been discussed here, but while thinking about using the OCZ Vertex 2 Pro SSD (which according to spec page has supercaps built in) as a shared slog and L2ARC device it stroke me that this might not be a such a good idea. Because this SSD is MLC based, write cycles are an issue here, though I can''t find any number in their spec. Why do I

On 2/8/2016 9:54 PM, Chris Murphy wrote: > Secure erase is really the only thing to use on SSDs. Writing a pile > of zeros just increases wear (minor negative) but also doesn't > actually set the cells to the state required to accept a new write, so > you've just added a lot more work for the SSD's garbage collector and > wear leveling, so it's going to be slower

A few wild ideas/questions : 1) Is there a way to check the size of the journal of an ext3 filesystem ? I mean - the actually used size ; not the total size of the journal. 2) Would it be difficult to implement "freeze" of ext3 filesystem - that is, blocking all I/O to the filesystem until it's "unfrozen" (XFS can do that), for two purposes : A/ allowing

On Thu, Aug 29, 2013 at 12:56:35PM +0100, Mark Ballard wrote: > I think this is really an attempt at user feedback, rather than user > discussion. But there's no such thing as a user-feedback mail list. > > Nevertheless, others may find this pertinent: why doesn't mke2fs > handle USB's competently? And if it does, why doesn't it reassure me > so? And how can I

Agh. This is great to have some of this clarified, Ted. It does unfortunately reinorce my cynicism. But it also fills my heart. That is, though it might be bad news to hear that I have most likely bought a piece of crap, and that there's no way I can really tell what's inside the cover unless either I do some kind of low-level alchemy of a kind that mere users would normally be well

> > From: "Esh, Andrew" <AEsh@tricord.com> > Date: Tue 10/Dec/2002 15:03 GMT > To: "'kevin.clarke@lister-petter.co.uk'" <kevin.clarke@lister-petter.co.uk>, > samba-technical@lists.samba.org > CC: "'samba@lists.samba.org'" <samba@lists.samba.org> > Subject: RE: Samba connecting to NT PDC > > (Please take

I think this is really an attempt at user feedback, rather than user discussion. But there's no such thing as a user-feedback mail list. Nevertheless, others may find this pertinent: why doesn't mke2fs handle USB's competently? And if it does, why doesn't it reassure me so? And how can I handle a linux-formatted USB flash drive in the absence of my system giving me any guidance?

I've been thinking of making a (mostly) solid-state asterisk pbx. Take either centos or some other distro, cut it down to bare minimum and put asterisk + AMP on. Something that could be put onto a usb2.0 flash stick, bootable. Modern flash devices (usb, compactflash) have builtin wear leveling management and will last longer than you think: