similar to: ext2 inode size patch - RE: PR kern/124621

Check if some pointers are not NULL due to read errors or other problems Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- core/fs/ext2/ext2.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/core/fs/ext2/ext2.c b/core/fs/ext2/ext2.c index bddde8d..8f0f2a4 100644 --- a/core/fs/ext2/ext2.c +++ b/core/fs/ext2/ext2.c @@ -139,6 +139,8 @@

The ext2 filesystem supports volume UUID now. The FSUUID variable can be set to kernel command line. Patch is based on FSUUID for FAT patch. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- core/fs/ext2/ext2.c | 40 +++++++++++++++++++++++++++++++++++++++- core/fs/ext2/ext2_fs.h | 1 + 2 files changed, 40 insertions(+), 1 deletion(-) diff --git a/core/fs/ext2/ext2.c

Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK? There is code for a "check" option for mount if these options are enabled, but there's no way to enable them. TIA Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

No material changes are made. --- Makefile | 10 +- convert.c => convert/convert.c | 803 +--------------------------------------- convert/convert.h | 76 ++++ convert/ext2.c | 791 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 873 insertions(+), 807 deletions(-) rename convert.c => convert/convert.c (74%) create mode

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

Hello, I was wondering if anyone could point me in the right direction? I am receiving these in my log file and do not know what they mean or what to look for; Mar 8 04:03:56 bms kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 8 04:03:56 bms kernel: ata3.00: cmd 25/00:28:42:d3:37/00:00:13:00:00/e0 tag 0 cdb 0x0 data 20480 in Mar 8 04:03:56 bms kernel: res

Hello, R-folks: Here is a statement I use to make a data frame: iccdata <- data.frame(i=rep(1:10,rep(2,10)),j=rep(1:2,10), x=c(0.35011,0.11989,0.13081,0.09919,0.16000,0.12000,0.00000,0.00000, 0.44023,0.32977,2.67081,2.63919,0.09050,0.03950,0.44019,0.30981,0.59000, 0.57000,4.03000,3.77000)) Then here are the data: > iccdata i j x 1 1 1 0.35011 2 1 2 0.11989 3 2 1 0.13081 4

Hi, This branch contains the new ext4's inline data support which has been added recently to kernel 3.8. In addition to inline data support, there are other patches that remove trainling whitespaces and extra new lines in ext2fs code and the other adds an assert() macro to Syslinux core. I think it's worth mentioning that these changes were made against master branch.

Sorry my bad, thanks for spotting it. Should that explains also the failure to grab the mutex? Andrea Il 3/12/2019 12:14 PM, Rowland Penny via samba ha scritto: > On Tue, 12 Mar 2019 12:01:08 +0100 > Andrea Cucciarre' <acucciarre at cloudian.com> wrote: > >> The OS is OmniOS, the DC is Windows Server (not sure about the >> release), and below the smb.conf.

Hi, the two patches improve the way memory is handled in supermin, by cleanly exiting on memory allocation failures, and free'ing memory when not needed (to keep working and not run out of memory). Pino Toscano (2): Check for failures in memory allocations Free memory buffers when not used src/ext2fs-c.c | 13 +++++++++++-- src/init.c | 13 +++++++++++++ 2 files changed, 24

Please forgive any stupidity in the following question. The admin who maintained samba left recently and we (a bunch of programmers) are trying to fix it. We had a Solaris box called svr2, it provided samba and nfs services. We bought a new computer called originally newsvr2. We ported the samba settings across to newsvr2 - everything worked. We swapped the hostname and IP addresses of svr2 and

Here is the initial release: git://github.com/donhiatt/Syslinux-EXT2FS-Library-port.git I am very new to git so I hope I managed to get the repo setup properly. The repo is branched from 'disklib' as I plan to use it for all disk read/write access (I'm currently using modified gpllib/disk/* -- see README). Cheers, don ----- README for ext2fs module. * Description -----------

Use the right formatting placeholders, so it gives no warnings also on 32bit platforms. --- src/ext2fs-c.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/ext2fs-c.c b/src/ext2fs-c.c index e45980a..cb9282b 100644 --- a/src/ext2fs-c.c +++ b/src/ext2fs-c.c @@ -31,6 +31,7 @@ #include <limits.h> #include <errno.h> #include <assert.h> +#include

Hi, I've noticed some general instability with plugging in or removing USB devices with FreeBSD 7.x, even when the devices are not actively in use. I had this happen with umass and ucom devices 3 times today. The machine hangs solid, there are no obvious signs of a panic or trap to DDB. I can't provide backtraces unfortunately -- these hangs happen on both my laptop and desktop, and

Hi, to ease debugging issues with appliances (e.g. when used in libguestfs), using --include-packagelist will add a file containing the list of all the packages used. Thanks, Pino Toscano (3): ext2: add ext2fs_chmod and ext2fs_chown chroot: factor out file copy code Add --include-packagelist src/build.ml | 42 +++++++++++++++++++++++++------ src/chroot.ml | 29

Hi! I'm trying to set up a SIP trunk so that I can test calls, etc., between a new Asterisk box, and an old 1.4 box. --------------------------------------------------------------------------- New box: root at asterisk1:/etc/asterisk# head -1 sip.conf #include siptrunk.conf siptrunk.conf: [box1] ; All box1 extensions; see extensions.conf type=peer context=adhearsion host=172.17.0.17 ; IP

Hi, I noticed that mount_ext2 isn't "connected" to the normal "buildworld" but sys/*/ext2fs seems to. Building and using it from recent RELENG_7 sources works for me (having ext2fs loaded as module in GENERIC). I mounted an ext3 rw, edited grub's menu.lst, wrote and umounted without any problems. It seems recent bugs got pathched in January

Was wondering if someone could tell me if this is correct. I want to set up some DFS shares. I have 3 servers with SAMBA/LDAP on them. My first is basically my PDC and the other two are my BDCs. I assume that I will have to set all of this up on each server, so that no matter which server catches the logon, the logon script will get run. Also, if one of the servers was to go down for a

Check early that there are enough free blocks to store each file, erroring out with ENOSPC if not; this avoids slightly more obscure errors later on. --- src/ext2fs-c.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/ext2fs-c.c b/src/ext2fs-c.c index f01ca9d..e45980a 100644 --- a/src/ext2fs-c.c +++ b/src/ext2fs-c.c @@ -52,6 +52,9 @@ /* fts.h in glibc is broken,

As per ext4 specification: > In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the > block group descriptor was only 32 bytes long and therefore ends at > bg_checksum. On an ext4 filesystem with the 64bit feature enabled, the > block group descriptor expands to at least the 64 bytes described below; > the size is stored in the superblock. Since block group