search for: dir_data

...c */ +#ifndef PATH_MAX +# ifdef NAME_MAX +# define PATH_MAX NAME_MAX +# elif FILENAME_MAX +# define PATH_MAX FILENAME_MAX +# else +# define PATH_MAX 256 +# endif /* NAME_MAX */ +#endif /* PATH_MAX */ + + +#define DIR_METATABLE "directory metatable" +typedef struct dir_data { + int closed; + DIR *dir; +} dir_data; + + +#define STAT_STRUCT struct stat +#define STAT_FUNC stat_via_fstat + +/* Emulate stat via fstat */ +int stat_via_fstat (const char *path, struct stat *buf) +{ + int fd = open (path, O_RDONLY); + if (fd == -1) { + DIR *dir = opendir (p...

"H. Peter Anvin" <hpa at zytor.com> writes: > On 08/29/2013 04:14 AM, Ferenc Wagner wrote: > >> "H. Peter Anvin" <hpa at zytor.com> writes: >> >>> On 08/22/2013 10:20 AM, Ferenc Wagner wrote: >>> >>>> Now that Syslinux has ls.c32 and lua.c32, it should be possible to build >>>> a customizable boot menu in

Hi, This series targets automatic boot menu generation, but most of it is the Lua upgrade, because I got tired reading deprecated API docs. It's mostly a straightforward forward port of the earlier Syslinux specific changes to Lua 5.1, except that: * I chose the add a stub getenv() implementation to the COM32 API instead of #ifdefing out all the references in Lua, and * I kept oslib

Hi all, I supose the subject is descriptive enough. In a CentOS server I do the next to make the daily backups: tar cfv - dir_data/ | openssl enc -e -salt -aes256 -pass pass:$PASSWORD -out backup_file.bin So I get an well-encrypted and tared file. If I want to decrypt and the file is easy in Unix/Linux environment: openssl enc -d -aes256 -in backup_file.bin | tar xfv - -C dir_what_you_want/ But the problem I currently have...

...op_ret = sys_lremovexattr (filler->real_path, key); 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> op_ret = sys_lremovexattr (real_path, name); 7 6811 xlators/storage/posix/src/posix.c <<init>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); So there are only two possibilities: 1) Source directory in ec/afr doesn't have gfid 2) Something else removed these xattrs. What is your volume info? May be that will give more clues. PS: sys_fremovexattr is called only from posix_fremovexattr...

...op_ret = sys_lremovexattr (filler->real_path, key); 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> op_ret = sys_lremovexattr (real_path, name); 7 6811 xlators/storage/posix/src/posix.c <<init>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); So there are only two possibilities: 1) Source directory in ec/afr doesn't have gfid 2) Something else removed these xattrs. What is your volume info? May be that will give more clues. PS: sys_fremovexattr is called only from posix_fremovexattr()...

...lremovexattr (filler->real_path, key); > 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> > op_ret = sys_lremovexattr (real_path, name); > 7 6811 xlators/storage/posix/src/posix.c <<init>> > sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); > > So there are only two possibilities: > > 1) Source directory in ec/afr doesn't have gfid > > 2) Something else removed these xattrs. > > What is your volume info? May be that will give more clues. > > > > PS...

...ller->real_path, key); >> 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> >> op_ret = sys_lremovexattr (real_path, name); >> 7 6811 xlators/storage/posix/src/posix.c <<init>> >> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); >> >> So there are only two possibilities: >> >> 1) Source directory in ec/afr doesn't have gfid >> >> 2) Something else removed these xattrs. >> >> What is your volume info? May be that will give mor...

...th, key); >>> 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> >>> op_ret = sys_lremovexattr (real_path, name); >>> 7 6811 xlators/storage/posix/src/posix.c <<init>> >>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); >>> >>> So there are only two possibilities: >>> >>> 1) Source directory in ec/afr doesn't have gfid >>> >>> 2) Something else removed these xattrs. >>> >>> What is your volume...

3.7.19 Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] Sent: Friday, July 07, 2017 11:54 AM To: Ankireddypalle Reddy Cc: Gluster Devel (gluster-devel at gluster.org); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at

...t;>> 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> >>>> op_ret = sys_lremovexattr (real_path, name); >>>> 7 6811 xlators/storage/posix/src/posix.c <<init>> >>>> sys_lremovexattr (dir_data->data, >>>> "trusted.glusterfs.test"); >>>> >>>> So there are only two possibilities: >>>> >>>> 1) Source directory in ec/afr doesn't have gfid >>>> >>>> 2) Something else removed these xattrs. >...

...op_ret = sys_lremovexattr (filler->real_path, key); 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> op_ret = sys_lremovexattr (real_path, name); 7 6811 xlators/storage/posix/src/posix.c <<init>> sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); So there are only two possibilities: 1) Source directory in ec/afr doesn't have gfid 2) Something else removed these xattrs. What is your volume info? May be that will give more clues. PS: sys_fremovexattr is called only from posix_fremovexattr()...

...lremovexattr (filler->real_path, key); > 6 5101 xlators/storage/posix/src/posix.c <<posix_removexattr>> > op_ret = sys_lremovexattr (real_path, name); > 7 6811 xlators/storage/posix/src/posix.c <<init>> > sys_lremovexattr (dir_data->data, "trusted.glusterfs.test"); > > So there are only two possibilities: > > 1) Source directory in ec/afr doesn't have gfid > > 2) Something else removed these xattrs. > > What is your volume info? May be that will give more clues. > > > > PS...

On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > Pranith, > > Thanks for looking in to the issue. The bricks were > mounted after the reboot. One more thing that I noticed was when the > attributes were manually set when glusterd was up then on starting the > volume the attributes were again lost. Had to stop glusterd