search for: deletem

Hi helpeRs, I have inherited a set of data files that use the file system as a sort of poor man's database, i.e., the data files are nested in directories that indicate which city they come from. For example: dir.create("deleteme") for(i in paste("deleteme", c("New York", "Los Angeles"), sep="/")) { dir.create(i) for(j in paste("data", 1:2, ".csv", sep="")) { write.csv(data.frame(x=1:10), file=paste(i, j, sep="/")) } }...

...ow I wish to delete the contents of the trash folder and the folder itself. This I cannot do. I have tried deleting using rm -rf ./.Trash-root but the command simply has no effect. It raises no error and it does not remove the Directory or its contents. For convenience I renamed the directory to DeleteME using move, which worked. As expected through, all attempts to remove DeleteME still fail silently. The permission bits are set thus: dr-xr-xr-x 1 root root 488 Oct 21 10:54 DeleteMe I have tried chmod -R 777 DeleteMe but this has no effect on the permissions. How do I get rid of this thing?...

...d include LVM and mdadm info as well, since I use those features.? I encourage you to look at what long-lived tools, such as clonezilla, write into their archive directories.? It's impressive. > > If you zero out all free space on all of your HDD partitions (dd bs=1M if=/dev/zero of=/path/deleteme; rm /path/deleteme) or use 'fstrim' for SSD's, you could use dd to image with fast & light compression (lzop or my current favorite, pzstd) and get maximum benefit of a bit-by-bit archival copy. > > > On 11/16/20 11:02 PM, H wrote: >> Short of backing up entire disks...

...fault:user:root:rwx default:group::--- default:group:somedom\\domain\040users:rwx default:mask::rwx default:other::--- The subfolder that 'vfs modules' created in the recycle share: /srv/www/htdocs/Papierkorb # ll insgesamt 0 drwxr-x---+ 1 somedom\fuhs somedom\domain users 16 22. Okt 11:39 deleteme getfacl deleteme/ # file: deleteme/ # owner: somedom\\fuhs # group: somedom\\domain\040users user::rwx user:root:rwx #effective:r-x group::--- group:somedom\\domain\040users:rwx #effective:r-x mask::r-x other::--- default:user::rwx default:user:root:rwx default:group::--- default:group:so...

centos 6 failed to create entries under /dev for newly created loopback devices. Any one know why? and how to fix/workaround it? The steps to duplicate is pretty simple dd if=/dev/zero of=/tmp/deleteme bs=1M count=100 losetup /dev/loop0 /tmp/deleteme fdisk /dev/loop0?? ## created partitions 1, 2, etc. fdisk -l /dev/loop0? ## confirmed that the partitions do exist mkfs.ext3 /dev/loop0p1 ## failed here, the error prompt says that the /dev/loop0p1 doesn't exist! ls /dev/loop0p*? ## no entries...

...ATUS_ACCESS_DENIED is coming from se_access_check(), because the delete bit is not cleared, but I really lack the context to understand WHY. I would greatly appreciate your assistance. I've run through as simple an interaction as I can think of: using smbclient to attempt to delete a "deleteme" file. I set debug logging to 10 for this example, and collected a client-specific log. I believe the key log line may be line 1599: [2015/04/26 00:07:17.457393, 10, pid=22294, effective(1001, 1001), real(1001, 0)] ../source3/smbd/open.c:171(smbd_check_access_rights) smbd_check_access_...

...k up /home to an external USB drive. Both drives are JFS. Example, where /media/8c4d270d-6139-4fed-8a32-2df8d28acdf3/ is the mount point for the external drive on which a back-up already exists: mike at robots mike]$ pwd /media/8c4d270d-6139-4fed-8a32-2df8d28acdf3/mike [mike at robots mike]$ mkdir deleteme1 [mike at robots mike]$ cd deleteme1/ [mike at robots deleteme1]$ touch deleteme1.txt [mike at robots deleteme1]$ cd ../Desktop [mike at robots Desktop]$ mkdir deleteme2 [mike at robots Desktop]$ cd deleteme2/ [mike at robots deleteme2]$ touch deleteme2.txt [mike at robots deleteme2]$ rsync -avn -...

Short of backing up entire disks using dd, I'd like to collect all required information to make sure I can restore partitions, disk information, UUIDs and anything else required in the event of losing a disk. So far I am collecting information from: - fdisk -l - blkid - lsblk - grub2-efi.cfg - grub - fstab Hoping that this would supply me with /all/ information to restore a system - with the

...(), because the > > delete bit is not cleared, but I really lack the context to understand > > WHY. I would greatly appreciate your assistance. > > > > I've run through as simple an interaction as I can think of: using > > smbclient to attempt to delete a "deleteme" file. I set debug logging > > to 10 for this example, and collected a client-specific log. I > > believe the key log line may be line 1599: > > > > [2015/04/26 00:07:17.457393, 10, pid=22294, effective(1001, 1001), > > real(1001, 0)] ../source3/smbd/open.c:...

Hi, OS : Solaris 10 11/06 zpool list doesn''t reflect pool usage stats instantly. Why? # ls -l total 209769330 -rw------T 1 root root 107374182400 Apr 30 14:28 deleteme # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT wo 136G 100G 36.0G 73% ONLINE - # rm deleteme # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT wo 136G 100G 36.0G 73...

...net Reporter: arden at metronet.co.uk QA Contact: rsync-qa at samba.org When using rsync with the -x (or --one-file-system) option to sync to a destination that crosses filesystems: --delete won't delete files in the second filesystem. Example done on a Centos7 machine where deleteme1 is left in the destination after deleting from the source: ------------------ root at arden-lt ~]# ## Setup environment in lvm root at arden-lt ~]# cd /tmp [root at arden-lt tmp]# VG=vg_ardenkvm [root at arden-lt tmp]# mkdir testsrc testdst [root at arden-lt tmp]# lvcreate -l 1 $VG/lvtest1 V...

...ete bit is not cleared, but I really lack the context to understand > >>> WHY. I would greatly appreciate your assistance. > >>> > >>> I've run through as simple an interaction as I can think of: using > >>> smbclient to attempt to delete a "deleteme" file. I set debug logging > >>> to 10 for this example, and collected a client-specific log. I > >>> believe the key log line may be line 1599: > >>> > >>> [2015/04/26 00:07:17.457393, 10, pid=22294, effective(1001, 1001), > >>> r...

I would include LVM and mdadm info as well, since I use those features.? I encourage you to look at what long-lived tools, such as clonezilla, write into their archive directories.? It's impressive. If you zero out all free space on all of your HDD partitions (dd bs=1M if=/dev/zero of=/path/deleteme; rm /path/deleteme) or use 'fstrim' for SSD's, you could use dd to image with fast & light compression (lzop or my current favorite, pzstd) and get maximum benefit of a bit-by-bit archival copy. On 11/16/20 11:02 PM, H wrote: > Short of backing up entire disks using dd, I'...

...adm info as well, since I use those >features.? I encourage you to look at what long-lived tools, such as >clonezilla, write into their archive directories.? It's impressive. >> >> If you zero out all free space on all of your HDD partitions (dd >bs=1M if=/dev/zero of=/path/deleteme; rm /path/deleteme) or use >'fstrim' for SSD's, you could use dd to image with fast & light >compression (lzop or my current favorite, pzstd) and get maximum >benefit of a bit-by-bit archival copy. >> >> >> On 11/16/20 11:02 PM, H wrote: >>> Shor...

...ming from se_access_check(), because the > delete bit is not cleared, but I really lack the context to understand > WHY. I would greatly appreciate your assistance. > > I've run through as simple an interaction as I can think of: using > smbclient to attempt to delete a "deleteme" file. I set debug logging > to 10 for this example, and collected a client-specific log. I > believe the key log line may be line 1599: > > [2015/04/26 00:07:17.457393, 10, pid=22294, effective(1001, 1001), > real(1001, 0)] ../source3/smbd/open.c:171(smbd_check_access_rig...

...sing FTP, I get the same both ways (30mbits/s)... I don't know why my from Samba to Windows speed is slower than the other direction, but the speed is not bad for a Pentium 100, so i'm not complaining. What do you get on your Unix system if you run this: date && dd if=/dev/zero of=deleteme.now count=100000 && rm deleteme.now && date (it creates a 51200000 byte file from random /dev/zero and gives you the time of both starting and ending) For the Pentium 100, I get about 3750kBytes/s, so my samba performance pretty well reflects disk performance on the FreeBSD system...

...tand how the amd map key(s) lookup process works. I've carefully read the am-utils(amd) document at http://am-utils.org/docs/am-utils/am-utils_8.html, especially the chapter "3.2 How keys are looked up" but am still not clear. For example, I'd like to access /home/dumbboy/files/deleteme, what is the key to be used, and how the lookup/match happens? and how the mount operations happens? Thanks a lot. I've attached my configuration files below: $ cat /etc/amd.conf ... auto_dir = /.amd_mnt ... map_type = file search_path = /etc ... [ /home...

...sys sysfs defaults 0 0 /dev/xvda2 /tmp ext3 defaults 0 0 /dev/xvda3 swap swap defaults 0 0 ** Problem ** While doing some tests writing files in domU I got; # dd if=/dev/zero of=/deleteme bs=1M count=100 100+0 records in 100+0 records out # dd if=/dev/zero of=/tmp/deleteme bs=1M count=100 end_request: I/O error, dev xvda2, sector 366778 end_request: I/O error, dev xvda2, sector 366844 end_request: I/O error, dev xvda2, sector 381116 printk: 8071 messages suppressed. Buffer I/O err...

Hi, what is Samba speed limit? I usually get maximum throughoutput about 3-4 MBytes/s reading from Samba, 2-3 MB/s writing to Samba server. (IDE discs, but 256 MB memory, Athlon 900 MHz, one 500 MB file, 100 Mbit network). What are your results? Does anybody knows about some performance tunings? I have adjusted only this: socket options = TCP_NODELAY SO_RCVBUF=16384 SO_SNDBUF=16384 write cache

...the >>> delete bit is not cleared, but I really lack the context to understand >>> WHY. I would greatly appreciate your assistance. >>> >>> I've run through as simple an interaction as I can think of: using >>> smbclient to attempt to delete a "deleteme" file. I set debug logging >>> to 10 for this example, and collected a client-specific log. I >>> believe the key log line may be line 1599: >>> >>> [2015/04/26 00:07:17.457393, 10, pid=22294, effective(1001, 1001), >>> real(1001, 0)] ../source3/...