search for: dshaw

Hello, I understand the need for a proper stride setting when formatting a filesystem on a RAID device. However, is there any problem in using a stride setting when formatting a filesystem on a regular non-RAID, non-SSD, just plain-vanilla-single-disk block device? I'm sure there isn't any benefit to it, but I'm curious if there is any harm. The reason I ask is I'm looking at

I am running Asterisk@Home Voicemail works fine but does not email out the voicemail attachments. Any suggestion? ----------------------------------- Voicemail.conf [general] #include vm_general.inc #include vm_email.inc [default] 201 => {password},Jeff G Laptop,jrglass@columbus.rr.com,,attach=yes --------------------------------------------------------------------- Sip.Conf [201]

I'm currently working with a testing system that involves running mkfs.ext3 on some pretty large devices on a regular basis. This is getting fairly painful, and I was wondering if there was some way to speed this up. Understood that the end result might be a filesystem that has less of a safety factor (say, fewer superblock backups) but the tradeoff might be worth it in this case. David

I have an odd problem that involves clients deleting files they should not be able to delete, and claiming success, but then the files "come back" again. Here's the setup: I have a filesystem that contains a file "foobar.txt" owned by user "test", group "test". Permissions on this file are 644, permissions on the enclosing directory are 777. I share

I am trying to export a Fuse filesystem filesystem via Samba (Samba 3.0.7, latest CVS Fuse on kernel 2.6.10). Fuse (http://fuse.sourceforge.net) is a library and kernel module to allow writing filesystems in userspace. I'm having a problem, however, in one odd place. Basically, the export works, and files are readable. However, when putting a new file in via drag-and-drop, windows (XP)

Hello, I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: menuentry 'boot ISO image' { linux16 /memdisk iso initrd16 /my-image.iso.gz } When selected, this starts to boot and then fails with: Ramdisk at 0x37979000, length 0x0033b298 gzip image: decompressed addr 0x7f7f7000, len

I have seen this happen a number of times: Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 kernel: Aborting journal on device sda5. Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 last message repeated 6 times Jun 13 13:58:18 n202 kernel: ext3_abort