similar to: To discard... or not to discard...

Hey everybody! I have a problem with triming a string. I can get rid of the blank space in front and at the back of a string and even trim a string at the back. But I don't know how to do it in the front. For Example: I have a string "Blackberry" and i want to delete the first 5 characters to get just "berry". Tnx for your help -- View this message in context:

On Friday, 5 August 2016 12:22:45 CEST Richard W.M. Jones wrote: > Because we run the external fstrim command we don't have access to the > kernel errno when it fails. However in the case where it prints this > specific error message, turn that into errno ENOTSUP. > --- Can you please note this behaviour in the documentation of the fstrim API? Thanks, -- Pino Toscano

Hello, I recently built a System out of old Computer parts I had. I installed Ubuntu 9.10 in it. I built it for sharing all my files with my other computer at home. I'm tired of having so many external Hard Drives. So, I built this new/old system and installed an old Seagate 500GB hard drive I've just RMAed. I'm able to share all my files with Windows Vista & 7 without any issues

I think I found a bug affecting btrfs filesystems and users invoking fstrim to discard unused blocks: if I execute a `fstrim -v /` twice, the amount trimmed does not change on the 2nd invocation AND it takes just as long as the first.  Why do I think this is a bug?  When I do the same on an ext4 partition I get different behavior: the output shows 0 B trimmed and it does is instantaneously when I

Here's a fun one: + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit + virt-sparsify --in-place test-virt-sparsify-in-place-fstrim-unsupported.img + tee test-virt-sparsify-in-place-fstrim-unsupported.log [ 2.4] Trimming /dev/sda1 [ 7.5] Sparsify in-place operation completed with no errors + grep 'warning:.*fstrim'

On Thu, April 2, 2015 17:11, J Martin Rushton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sorry to mention the "opposition" here, but I have a family member's > laptop to protect, and I'm not allowed to upgrade it to Linux. What's > the current best recommendation? > Thanks, We (Harte & Lyne Limited) formerly used F-Prot out of

On 04/04/2016 12:11 PM, Jussi Hirvi wrote: > This made me google around a little, and I found some good info here. > They, too, kind of recommend openvpn. > http://www.howtogeek.com/211329/which-is-the-best-vpn-protocol-pptp-vs.-openvpn-vs.-l2tpipsec-vs.-sstp/ > This is not good information. In brief: "There are some concerns that the NSA could have weakened the standard,

On Thu, 27 Jun 2019, Peda, Allan (NYC-GIS) wrote: > I'd isolate all that RAID stuff from your OS, so the root, /boot, /usr, /etc /tmp, /bin swap are on "normal" partition(s). I know I'm missing some directories, but the point is you should be able to unmount that RAID stuff to adjust it without crippling your system. > >

On Wed, Sep 05, 2018 at 04:41:01PM +0100, Daniel P. Berrangé wrote: > On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote: > > > > Here's a fun one: > > > > + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit > > + virt-sparsify --in-place test-virt-sparsify-in-place-fstrim-unsupported.img > > + tee

Adding an option for initrdfile= boot argument to be ignored by wimboot worked just fine. They can add this patch, which is probably most sane, or syslinux could add the INITRDFILE configuration option instead of having to append the option for linux.c32 wimboot-2.4.0/src/cmdline.c @ Line ~107 } else if ( key == cmdline ) { /* Ignore unknown initial

Since Linux commit f663b5b38fff trimming vfat is now supported by Linux. This broke the test which assumed it was not supported. Use another filesystem (minix) which does not support trimming instead. Thanks: Daniel P. Berrangé and Pino Toscano. --- ...virt-sparsify-in-place-fstrim-unsupported.sh | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git

Because we run the external fstrim command we don't have access to the kernel errno when it fails. However in the case where it prints this specific error message, turn that into errno ENOTSUP. --- daemon/fstrim.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/daemon/fstrim.c b/daemon/fstrim.c index 1ad3630..527acfd 100644 --- a/daemon/fstrim.c +++

I still get the "the discard operation is not supported" fstrim error when the LVs are set to "nopassdown" Seems that when I use ext4 the fstrim reports that it worked but the LVs Data% does not decrease after the fstrim. xfs just throws the error. I've also been looking at the output of lsblk -D # lsblk -D NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO xvdb

This reverts the change made for RHBZ#1168144. The warning is now always displayed. It would be nice to make the warning actionable, but there is not a lot that end users can do since fstrim is such a complex topic interacting with all filesystem and storage layers. --- v2v/v2v.ml | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/v2v/v2v.ml b/v2v/v2v.ml index

Hi All I'm trying to setup my LVM thin pool to support discards so that the pool can reclaim space even if the underlying device doesn't support trim. It is my understanding that all thin pools should support trim even if the underlying device doesn't. (please correct me if I'm wrong here) I have one centos server that does support trim and everything is working correctly but any

On Fri, Aug 12, 2016 at 04:50:31PM +0200, Pino Toscano wrote: > On Friday, 12 August 2016 10:37:29 CEST Richard W.M. Jones wrote: > > This reverts the change made for RHBZ#1168144. The warning is now > > always displayed. > > > > It would be nice to make the warning actionable, but there is not a > > lot that end users can do since fstrim is such a complex topic

On Wed, Oct 15, 2014 at 12:03:26PM +0000, VONDRA Alain wrote: > Rich, > The results of the guestfish command : > > ><fs> part-list /dev/sda > [0] = { > part_num: 1 > part_start: 1048576 > part_end: 85906685951 > part_size: 85905637376 > } > ><fs> part-list /dev/sdb > [0] = { > part_num: 1 > part_start: 32256 > part_end:

Hi, I'm trying to find out how to enable fstrim support for libvirt/qemu guests. Specifically I'm trying to enable this on a CentOS 7 host (qemu 1.5). I searched the web but only found very vague information and no clear documentation on the requirements or how to modify the guest xml to enable discard/fstrim support. Can someone point me in the right direction? Regards, Dennis

On Mon, Nov 3, 2014 at 4:24 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 01.11.2014 05:30, Dennis Jacobfeuerborn wrote: >> >> Hi, >> I'm trying to find out how to enable fstrim support for libvirt/qemu >> guests. Specifically I'm trying to enable this on a CentOS 7 host (qemu >> 1.5). I searched the web but only found very vague information

Hello, I'm trying to use a current Syslinux setup, that is working well for service linux based distros, to serve up recent Windows server installs. As I'm new here I'm reluctant to make any changes to the environment unless I've exhausted the current options. We are running Syslinux 3.71 on a Gentoo server and all the DHCP and tftpd are "working as they should". What